From: david.fox@lindows.com
To: caml-list@inria.fr
Subject: [Caml-list] Ouch - when bytecode and native behave differently
Date: 02 Oct 2002 07:55:54 -0700 [thread overview]
Message-ID: <8765wkao05.fsf@foxthompson.net> (raw)
I just encountered a situation where the bytecode and native versions
of a program behave differently. It turns out that out of bounds
array accesses return a different message:
Invalid_argument "Array.get"
vs.
Invalid_argument "out-of-bound array or string access"
I was catching the former but not the latter. I don't know if I'm
making a mistake by paying attention to the message or if this is a
problem or issue in the standard libs, but I thought I'd point it out.
Thanks,
-david
-------------------
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-10-03 7:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 14:55 david.fox [this message]
2002-10-03 8:11 ` Henri Dubois-Ferriere
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=8765wkao05.fsf@foxthompson.net \
--to=david.fox@lindows.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).