Browse thread
[Caml-list] Ouch - when bytecode and native behave differently
-
david.fox@l...
- Henri Dubois-Ferriere
[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
| Date: | -- (:) |
| From: | Henri Dubois-Ferriere <henridf@l...> |
| Subject: | Re: [Caml-list] Ouch - when bytecode and native behave differently |
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