You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original bug ID: 2025 Reporter: administrator Status: closed Resolution: fixed Priority: normal Severity: minor Category: ~DO NOT USE (was: OCaml general)
Bug description
On Sat, 27 Dec 2003, Damien Doligez wrote:
This bug is in fact in the ML part of the Num library, which is common
to both the old and new Num implementations. I think it dates back to
Caml Light.
(...)
This "nondeterminism" comes from using a Nat.nat with an uninitialised
digit, using whatever was already in memory at that address.
Many thanks for your prompt action. (By the way, ocaml is a very nice tool
for certain kinds of calculations in Superstring/M-Theory - see http://arxiv.org/abs/hep-th/0312262 .)
Original bug ID: 2025
Reporter: administrator
Status: closed
Resolution: fixed
Priority: normal
Severity: minor
Category: ~DO NOT USE (was: OCaml general)
Bug description
On Sat, 27 Dec 2003, Damien Doligez wrote:
Many thanks for your prompt action. (By the way, ocaml is a very nice tool
for certain kinds of calculations in Superstring/M-Theory - see
http://arxiv.org/abs/hep-th/0312262 .)
--
regards, tf@cip.physik.uni-muenchen.de (o_
Thomas Fischbacher - http://www.cip.physik.uni-muenchen.de/~tf //
(lambda (n) ((lambda (p q r) (p p q r)) (lambda (g x y) V_/_
(if (= x 0) y (g g (- x 1) (* x y)))) n 1)) (Debian GNU)
The text was updated successfully, but these errors were encountered: