From: Nicholas Clark <nick@ccl4.org>
Date: Thu, 15 May 2008 13:03:48 +0000 (+0000)
Subject: Add investigating eliminating POSIX::int_macro_int() to perltodo.
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=839c1407d250d7c1cabbabe92d598c29d94077e8;p=p5sagit%2Fp5-mst-13.2.git

Add investigating eliminating POSIX::int_macro_int() to perltodo.

p4raw-id: //depot/perl@33830
---

diff --git a/pod/perltodo.pod b/pod/perltodo.pod
index a75305f..81afdb0 100644
--- a/pod/perltodo.pod
+++ b/pod/perltodo.pod
@@ -551,6 +551,18 @@ These tasks would need C knowledge, and roughly the level of knowledge of
 the perl API that comes from writing modules that use XS to interface to
 C.
 
+=head2 investigate removing int_macro_int from POSIX.xs
+
+As a hang over from the original C<constant> implementation, F<POSIX.xs>
+contains a function C<int_macro_int> which in conjunction with C<AUTOLOAD> is
+used to wrap the C functions C<WEXITSTATUS>, C<WIFEXITED>, C<WIFSIGNALED>,
+C<WIFSTOPPED>, C<WSTOPSIG> and C<WTERMSIG>. It's probably worth replacing
+this complexity with 5 simple direct wrappings of those 5 functions.
+
+However, it would be interesting if someone could measure the memory usage
+before and after, both for the case of C<use POSIX();> and the case of
+actually calling the Perl space functions.
+
 =head2 safely supporting POSIX SA_SIGINFO
 
 Some years ago Jarkko supplied patches to provide support for the POSIX