From: Damien Doligez <Damien.Doligez@inria.fr>
To: barabh@qwest.net, caml-list@inria.fr
Subject: Re: [Caml-list] Error Reporting
Date: Thu, 27 Sep 2001 15:00:08 +0200 (MET DST) [thread overview]
Message-ID: <200109271300.PAA0000005731@beaune.inria.fr> (raw)
>From: "David McClain" <barabh@qwest.net>
>I am looking for some ideas on handling program error reporting for a
>compiler that is built largely on CPS. Since there are no stack frames to
>crawl for traceback, I have a first cut based on keeping a finite length
>queue of last visited closures.
It seems to me that the current continuation in a CPS program should
contain the same information as the stack in a stack-based program.
You have the problem of losing information on a tail-call in both
systems, for example. So you should be able to do as well as a stack
crawl with a "continuation crawl". Of course, this will depend on the
data structure used to represent continuations, and if you use normal
closures for that, you will be compiler-dependent, but again this is
no worse than the stack-based case.
Or am I missing something ?
-- Damien
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next reply other threads:[~2001-09-27 13:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-27 13:00 Damien Doligez [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-28 16:49 David McClain
2001-10-01 0:52 ` John Prevost
2001-10-01 14:17 ` Frank Atanassow
2001-10-01 15:44 ` David McClain
2001-09-27 13:32 Krishnaswami, Neel
2001-09-27 20:36 ` David McClain
2001-09-28 15:24 ` Frank Atanassow
2001-09-28 16:41 ` David McClain
2001-09-27 22:34 ` David McClain
2001-09-26 22:55 David McClain
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=200109271300.PAA0000005731@beaune.inria.fr \
--to=damien.doligez@inria.fr \
--cc=barabh@qwest.net \
--cc=caml-list@inria.fr \
/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).