Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unix module and Windows #8190

Closed
vicuna opened this issue Jun 27, 2003 · 1 comment
Closed

Unix module and Windows #8190

vicuna opened this issue Jun 27, 2003 · 1 comment

Comments

@vicuna
Copy link

vicuna commented Jun 27, 2003

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

@vicuna
Copy link
Author

vicuna commented Jun 30, 2003

Comment author: administrator

The Caml part of the Unix and Windows implementations of module Unix are too
different to allow this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant