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: 5566 Reporter: Hendrik Tews Assigned to:@alainfrisch Status: resolved (set by @alainfrisch on 2016-12-06T15:01:24Z) Resolution: fixed Priority: normal Severity: feature Version: 3.12.1 Fixed in version: 4.04.0 Category: standard library Monitored by: meurer mehdi @glondu@hcarty
Bug description
I would like to suggest to have the is_native flag also in module
Sys. This way, code running in the toplevel could distinguish
whether it is running inside ocaml or inside ocamlnat, in order
to decide whether it should call Topdirs.load_file with cmo or
cmxs arguments.
The text was updated successfully, but these errors were encountered:
Is that not enough? There's different Dynlink implementations in the source tree, so it's easy to define is_native as being true or false, but I'm not sure how we would do that inside the Sys module...
Having Sys.is_native is useful especially in those cases where
the dynlink library is not required. In those cases one doesn't
really want to load findlib and dynlink to access just one boolean.
One can always check at program invocation whether one is going
to run a native program and use different source code or
additional arguments for the native program.
Original bug ID: 5566
Reporter: Hendrik Tews
Assigned to: @alainfrisch
Status: resolved (set by @alainfrisch on 2016-12-06T15:01:24Z)
Resolution: fixed
Priority: normal
Severity: feature
Version: 3.12.1
Fixed in version: 4.04.0
Category: standard library
Monitored by: meurer mehdi @glondu @hcarty
Bug description
I would like to suggest to have the is_native flag also in module
Sys. This way, code running in the toplevel could distinguish
whether it is running inside ocaml or inside ocamlnat, in order
to decide whether it should call Topdirs.load_file with cmo or
cmxs arguments.
The text was updated successfully, but these errors were encountered: