From: Dave Berry <dave@kal.com>
To: Ohad Rodeh <orodeh@cs.huji.ac.il>, Pierre Weis <Pierre.Weis@inria.fr>
Cc: Mattias Waldau <mattias.waldau@abc.se>, caml-list@inria.fr
Subject: RE: Where did the exception occur?
Date: Mon, 30 Oct 2000 11:20:06 -0000 [thread overview]
Message-ID: <3145774E67D8D111BE6E00C0DF418B66339A40@nt.kal.com> (raw)
People seem to be confusing "language" and "implementation". MLWorks (a now
defunct implementation of SML) implemented "pop" semantics by "pushing" a
handler onto the stack, which enabled debugging of the stack from the
debugger. (Then again, MLWorks code couldn't be called from C, so Ohad's
case couldn't arise). Other implementations of SML may well report the line
number where the exception occurred: this is definitely a useful feature.
Dave.
-----Original Message-----
From: Ohad Rodeh [mailto:orodeh@cs.huji.ac.il]
Sent: Monday, October 30, 2000 7:57
To: Pierre Weis
Cc: Mattias Waldau; caml-list@inria.fr
Subject: Re: Where did the exception occur?
List,
I'd like to point out, that my application (LARGE OCaml project) is
embedded in C code, so one cannot use the OCaml debugger to replay and
find the exception. I'd be happy if a feature would be added to the
language to point out which line in the code the exception came from (I
understand this was added to SML ?).
Ohad.
next reply other threads:[~2000-10-30 14:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-30 11:20 Dave Berry [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-10-31 10:14 Damien Doligez
2000-10-31 12:09 ` Mattias Waldau
2000-10-31 16:52 ` Pierre Weis
2000-10-31 15:27 ` CREGUT Pierre FTRD/DTL/LAN
2000-10-30 15:21 David McClain
2000-10-30 15:19 David McClain
2000-10-30 15:09 Greg Morrisett
2000-10-30 14:39 Greg Morrisett
2000-10-29 9:59 Mattias Waldau
2000-10-30 7:36 ` Pierre Weis
2000-10-30 7:57 ` Ohad Rodeh
2000-10-30 11:02 ` Pierre Weis
2000-10-30 11:33 ` Stephan Houben
2000-10-30 12:12 ` David Mentré
2000-11-02 17:29 ` Pierre Weis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3145774E67D8D111BE6E00C0DF418B66339A40@nt.kal.com \
--to=dave@kal.com \
--cc=Pierre.Weis@inria.fr \
--cc=caml-list@inria.fr \
--cc=mattias.waldau@abc.se \
--cc=orodeh@cs.huji.ac.il \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).