On Tue, Aug 30, 2011 at 10:06 PM, Mark Overmeer <mark@overmeer.net> wrote: > I propose to start-off with the cleaned-up POSIX as dual-life for > 5.15. Then, invite the "CPAN" specialists of the missing compontents > to contribute their few lines of XS to the generic POSIX.xs, let it get > up-to-date. Sounds like a fine plan, but it would require some effort. Currently POSIX.xs can piggyback on perl's detection of various system functions and headers, if made standalone it needs to duplicate that. Fortunately, it's mostly something that has to be done only once. > POSIX.xs/pm should only provide the bare minimum interface, mapped as > narrow as possible on the functions where it can. Fancy OO models and > such around these functions should not be part of this. There's a difference between OO abstractions around system resources and OO abstractions around data. POSIX.pm is already doing the latter (POSIX::SigAction, POSIX::SigSet) and that makes perfect sense. Leon TimmermansThread Previous | Thread Next