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: 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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: