From: "Sanghyeon Seo" <sanxiyn@gmail.com>
To: caml-list@inria.fr
Subject: break and continue v2
Date: Sun, 13 Apr 2008 08:50:12 +0900 [thread overview]
Message-ID: <5b0248170804121650x78062d8m4c1d919a72e414b9@mail.gmail.com> (raw)
This is the revision of break/continue patch I sent.
http://sparcs.kaist.ac.kr/~tinuviel/devel/ocaml/
This patch no longer modifies lambda code, and uses static exception
instead. bytegen is restored, and break/continue target stack is moved
to translcore.
simplify_exits is modified to track whether exit is in tail position.
It no longer replaces exit with handler when exit is not in tail
position. This is done with two hash tables; I'd like to hear
suggestions for better implementation.
--
Seo Sanghyeon
reply other threads:[~2008-04-12 23:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5b0248170804121650x78062d8m4c1d919a72e414b9@mail.gmail.com \
--to=sanxiyn@gmail.com \
--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).