From: "Harry Chomsky" <harry@chomsky.net>
To: "Caml-list" <caml-list@inria.fr>
Subject: [Caml-list] Status of callback_exn bug
Date: Thu, 11 Jul 2002 10:28:40 -0700 [thread overview]
Message-ID: <004f01c22900$661387d0$0200a8c0@harry> (raw)
With all the talk about an upcoming release of OCaml 3.05, I thought I
should ask once more if anybody knows about the status of the callback_exn
bug that was reported on April 12, 2002 in
http://caml.inria.fr/archives/200204/msg00065.html
The CVS shows that a change was made to byterun/interp.c on that date, which
appears to be intended to fix the problem, but for me the problem remains
even with this fix. Is it possible that version 3.05 will really fix the
problem? If there's still more tweaking to be done, is it possible that it
could get done in time to be included in the release?
Thanks,
Harry
-------------------
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
next reply other threads:[~2002-07-11 17:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-11 17:28 Harry Chomsky [this message]
2002-07-11 18:50 ` Harry Chomsky
-- strict thread matches above, loose matches on Subject: below --
2002-06-10 20:04 Harry Chomsky
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='004f01c22900$661387d0$0200a8c0@harry' \
--to=harry@chomsky.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