Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0005157OCamlOCaml generalpublic2010-09-27 16:192014-02-06 12:30
Reporterkaustuv 
Assigned To 
PrioritynormalSeverityfeatureReproducibilityalways
StatusacknowledgedResolutionopen 
PlatformOSOS Version
Product Version3.12.0 
Target VersionFixed in Version 
Summary0005157: caml_convert_signal_number/caml_rev_convert_signal_number should not be private in caml/signals.h
DescriptionThere is apparently no way to go back and forth between the signal numbers defined in the Sys module and native signal numbers without breaking the caml API. This prevents the Unix module from being cleanly extended with non-POSIX signal operations, such as adding support for signalfd(2) on Linux.
TagsNo tags attached.
Attached Filespatch file icon pr5157.patch [^] (550 bytes) 2014-02-06 04:19 [Show Content]

- Relationships

-  Notes
(0010891)
kaustuv (reporter)
2014-02-06 04:23

This seems to have dropped off the radar. I just recently ran into this problem again when I had to bind a C library that does signal munging of its own. The fix is almost too trivial for words, but I've attached a patch nonetheless.

I understand that changing the caml api should not be done lightly as you limit your options for changes in the future. However, this particular feature of signals.h has been stable for a *very* long time.

- Issue History
Date Modified Username Field Change
2010-09-27 16:19 kaustuv New Issue
2011-05-20 15:52 doligez Status new => acknowledged
2014-02-06 04:19 kaustuv File Added: pr5157.patch
2014-02-06 04:23 kaustuv Note Added: 0010891


Copyright © 2000 - 2011 MantisBT Group
Powered by Mantis Bugtracker