From: "Sanghyeon Seo" <sanxiyn@gmail.com>
To: caml-list@inria.fr
Subject: break and continue for OCaml
Date: Thu, 10 Apr 2008 10:59:16 +0900 [thread overview]
Message-ID: <5b0248170804091859s75c3f725s2db53f48fba6735c@mail.gmail.com> (raw)
I have the first cut of patch to implement break and continue inside
for and while loops for OCaml.
http://sparcs.kaist.ac.kr/~tinuviel/devel/ocaml/
Patch is against OCaml 3.10.2. All the meat is in bytecomp/bytegen.ml.
Currently bytecode only. I am working on natvie code and error
handling when break is used outside loop etc but I thought "releasing
early" could be useful.
What do you think?
--
Seo Sanghyeon
next reply other threads:[~2008-04-10 1:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 1:59 Sanghyeon Seo [this message]
2008-04-10 7:09 ` [Caml-list] " Luc Maranget
2008-04-10 7:11 ` Jean-Christophe Filliâtre
2008-04-10 14:12 ` David Allsopp
2008-04-10 14:41 ` Richard Jones
2008-04-10 13:39 ` Richard Jones
2008-04-10 14:05 ` Martin Jambon
2008-04-10 14:19 ` Richard Jones
2008-04-10 14:24 ` Michael Wohlwend
2008-04-10 14:35 ` Martin Jambon
2008-04-10 14:38 ` Michael Wohlwend
2008-04-10 22:23 ` Florian Weimer
2008-04-10 20:35 ` Eric Cooper
2008-04-11 0:14 ` Micha
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=5b0248170804091859s75c3f725s2db53f48fba6735c@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