I executed the following code, the array a0 was allocated to match the
filesize and get32 reads 4 bytes via input_byte:
let idx = ref 0 in
try
while true do
a0.(!idx) <-get32 file;
incr idx;
done
with
End_of_file -> close_in file;
this code works as bytecode but gives an array exception when compiled to
native code. Is the execution order different on the two compilers? The a0.
(!idx) get evaluted before the get32 in native-code, but with bytecode the
get32 is computed first (it seems).
The code works if I add a temporary variable like:
let t = get32 file in
a0.(!idx) <- t;
is this a feature ? :-)
cheers,
Michael
_______________________________________________
Caml-list mailing list. Subscription management:
http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
Archives: http://caml.inria.fr
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
Bug reports: http://caml.inria.fr/bin/caml-bugs
You shouldn't rely on the order that these are executed. Normal
parameter evaluation (which this is not) in OCaml happens to be right
to left, but it's not defined to be that way. Use the let binding if
you depend on a particular ordering.
> let t = get32 file in
> a0.(!idx) <- t;
Rich.
--
Richard Jones, CTO Merjis Ltd.
Merjis - web marketing and technology - http://merjis.com
Team Notepad - intranets and extranets for business - http://team-notepad.com