From: Nicholas Clark <nick@ccl4.org>
Date: Sat, 17 Sep 2005 19:49:27 +0000 (+0000)
Subject: Add "refactor xsubpp to be a thin wrapper around ExtUtils::ParseXS"
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=8523e16436db8e26c8ddb2231ea32d0763c07741;p=p5sagit%2Fp5-mst-13.2.git

Add "refactor xsubpp to be a thin wrapper around ExtUtils::ParseXS"
to the TODO

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

diff --git a/pod/perltodo.pod b/pod/perltodo.pod
index 6fe7a67..6fe1fd6 100644
--- a/pod/perltodo.pod
+++ b/pod/perltodo.pod
@@ -227,6 +227,23 @@ that this is due to incomplete dependency specification in the F<Makefile>.
 It would be good if someone were able to track down the causes of these
 problems, so that parallel builds worked properly.
 
+=head2 Refactor C<xsubpp> to be a thin wrapper around C<ExtUtils::ParseXS>
+
+C<ExtUtils::ParseXS> encapsulates a version of the C<xsubpp> into a module.
+In effect this is a code fork, and it's likely that C<xsubpp> has had some
+bug fixes since the code from C<ExtUtils::ParseXS> was derived. It would be
+good to merge the differences in, reduce down to 1 canonical implementation,
+and convert C<xsubpp> to a very thin command line wrapper to
+C<ExtUtils::ParseXS>.
+
+In theory this needs no real C knowledge, as one way of approaching this task
+is to ensure that C<ExtUtils::ParseXS> generates identical output to C<xsubpp>
+for input XS files, which does not require understanding the contents of the
+output C file. However, some C knowledge is likely to help with testing, and
+locating/producing comprehensive test cases.
+
+
+
 
 
 =head1 Tasks that need a little C knowledge