caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Henri Dubois-Ferriere <henridf@lcavsun1.epfl.ch>
To: <david.fox@lindows.com>
Cc: <caml-list@inria.fr>
Subject: Re: [Caml-list] Ouch - when bytecode and native behave differently
Date: Thu, 3 Oct 2002 10:11:05 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.33.0210031007060.21678-100000@lcavpc19.epfl.ch> (raw)
In-Reply-To: <8765wkao05.fsf@foxthompson.net>

This is filed as bug 1347 in the ocaml 'bugzilla'

Another similar bug is that in bytecode, a divide-by-zero is reported as
"Fatal error: exception Division_by_zero", whereas in native you get
"Floating point exception".

Henri


> 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
>


-------------------
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


      reply	other threads:[~2002-10-03  8:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-02 14:55 david.fox
2002-10-03  8:11 ` Henri Dubois-Ferriere [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.LNX.4.33.0210031007060.21678-100000@lcavpc19.epfl.ch \
    --to=henridf@lcavsun1.epfl.ch \
    --cc=caml-list@inria.fr \
    --cc=david.fox@lindows.com \
    --cc=henri.dubois-ferriere@epfl.ch \
    /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).