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

Please export byterun/io.h #4121

Closed
vicuna opened this issue Sep 25, 2006 · 2 comments
Closed

Please export byterun/io.h #4121

vicuna opened this issue Sep 25, 2006 · 2 comments
Assignees

Comments

@vicuna
Copy link

vicuna commented Sep 25, 2006

Original bug ID: 4121
Reporter: @mmottl
Assigned to: @mshinwell
Status: resolved (set by @mshinwell on 2016-12-06T21:28:14Z)
Resolution: fixed
Priority: normal
Severity: feature
Version: 3.09.3
Category: ~DO NOT USE (was: OCaml general)
Monitored by: @mmottl

Bug description

It would be very useful for people who want to write custom I/O code using channels if byterun/io.h were exported, i.e. if this file were among the other header files that can already be accessed. Otherwise developers have to copy it from the distribution, which might break code if io.h gets updated in a new OCaml-release.

@vicuna
Copy link
Author

vicuna commented Sep 25, 2006

Comment author: @mmottl

Ok, this suggestion is actually not that trivial. It unfortunately requires that the configuration header files, etc., are also installed. I am not sure whether this is a good idea, but given that the installation is architecture specific anyway, it may be.

It might also be easy enough for users to just copy the type definition of the channel structure and use their own typedefs for e.g. the file_offset to make things work. But if there is an easy way to make use of the local OCaml-configuration, this would be even better.

@vicuna
Copy link
Author

vicuna commented Dec 6, 2016

Comment author: @mshinwell

Fixed by CAML_INTERNALS

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

2 participants