From: Alain Frisch <frisch@clipper.ens.fr>
To: Xingyuan Zhang <Xingyuan.Zhang@durham.ac.uk>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Question on interp.c
Date: Thu, 30 May 2002 18:06:40 +0200 (MET DST) [thread overview]
Message-ID: <Pine.SOL.4.44.0205301803360.27024-100000@clipper.ens.fr> (raw)
In-Reply-To: <3CF610BC.640425A1@durham.ac.uk>
On Thu, 30 May 2002, Xingyuan Zhang wrote:
> I am now reading the source of interp.c. I cannot see how the while (1)
> { ...} loop in interprete is terminated
> when the program reaches its end.
By return instructions in the handlers of the two following Caml abstract
machine instructions:
- RAISE (when the exception is not catched by an enclosing Caml handler)
- STOP
-- Alain
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
prev parent reply other threads:[~2002-05-30 16:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-30 11:45 Xingyuan Zhang
2002-05-30 16:06 ` Alain Frisch [this message]
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=Pine.SOL.4.44.0205301803360.27024-100000@clipper.ens.fr \
--to=frisch@clipper.ens.fr \
--cc=Xingyuan.Zhang@durham.ac.uk \
--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).