Mark Overmeer wrote: >Complete silence for three months followed. Yeah, sorry, we do that a lot. >POSIX.pm is a troublesome module. Aside from the manual page being >mistaken in countless places and the 150 separate single line autoloading >modules (which usually simply produce a "croak not implemented"), it is >on a stand-still for ages. Yes. It needs a maintainer who will put in the time to update it. >I see the module move in either of these two directions: > 1) clean-up the module as part of perl-core. > 2) give POSIX a dual-life (Zelfram's request to dual-life Carp just > comes in when I write this) and let it grow. Dual-lifing seems a natural direction to go if it's acquiring a maintainer. There's also a bit of the same feature issue that Carp has, but not as much as Carp because POSIX has been so static. Whether dual-lifing or not, now is a great time to submit patches to improve POSIX in core. -zeframThread Previous