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: 1733 Reporter: administrator Status: closed Resolution: won't fix Priority: normal Severity: feature Category: ~DO NOT USE (was: OCaml general)
Bug description
Full_Name: Wheeler Ruml
Version: 3.06
OS: Linux and mingw
Submission from: katsura.parc.xerox.com (13.2.18.21)
This must be old news, but I couldn't find a related previously-filed bug
report.
Bytecode that calls functions in the Unix module and is linked under a Unix
system doesn't run under Windows ("unix_fork" unknown), even if the code only
refers to functions that exist under Windows. It's a shame that this
unnecessarily breaks the portability of bytecode.
One way to fix this, suggested by Nicolas Cannasse, would be to implement all
the remaining functions under Windows, but just have them throw run-time
exceptions. Another way would be to separate the commonly-available and the
unix-only functions in separate modules.
Not a big deal, but I thought I'd bring it up.
Thanks for some great software!
Wheeler
The text was updated successfully, but these errors were encountered:
Original bug ID: 1733
Reporter: administrator
Status: closed
Resolution: won't fix
Priority: normal
Severity: feature
Category: ~DO NOT USE (was: OCaml general)
Bug description
Full_Name: Wheeler Ruml
Version: 3.06
OS: Linux and mingw
Submission from: katsura.parc.xerox.com (13.2.18.21)
This must be old news, but I couldn't find a related previously-filed bug
report.
Bytecode that calls functions in the Unix module and is linked under a Unix
system doesn't run under Windows ("unix_fork" unknown), even if the code only
refers to functions that exist under Windows. It's a shame that this
unnecessarily breaks the portability of bytecode.
One way to fix this, suggested by Nicolas Cannasse, would be to implement all
the remaining functions under Windows, but just have them throw run-time
exceptions. Another way would be to separate the commonly-available and the
unix-only functions in separate modules.
Not a big deal, but I thought I'd bring it up.
Thanks for some great software!
Wheeler
The text was updated successfully, but these errors were encountered: