From: skaller <skaller@users.sourceforge.net>
To: David McClain <dmcclain1@mindspring.com>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] C++ Stack Frames
Date: 28 Aug 2004 19:04:57 +1000 [thread overview]
Message-ID: <1093683896.15255.1774.camel@pelican.wigram> (raw)
In-Reply-To: <002801c48cb9$216fccf0$0401000a@dylan>
On Sat, 2004-08-28 at 14:40, David McClain wrote:
> What puzzles me, and at the same time, inspires admiration for the OCaml
> team, is that they somehow manage to neutralize these ascending escapes.
They don't. Its pure luck that C++ fails to find the handler.
--
John Skaller, mailto:skaller@users.sf.net
voice: 061-2-9660-0850,
snail: PO BOX 401 Glebe NSW 2037 Australia
Checkout the Felix programming language http://felix.sf.net
-------------------
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:[~2004-08-28 9:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-28 4:40 David McClain
2004-08-28 9:04 ` skaller [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=1093683896.15255.1774.camel@pelican.wigram \
--to=skaller@users.sourceforge.net \
--cc=caml-list@inria.fr \
--cc=dmcclain1@mindspring.com \
/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