X-Git-Url: https://perl5.git.perl.org/perl5.git/blobdiff_plain/1f2e791661e807f561a2d5dd8f2b6a4e339e444e..5a176cbce82d0ae2fd8e94d132259dfb733ef939:/pod/perltodo.pod
diff --git a/pod/perltodo.pod b/pod/perltodo.pod
index f7782c7..c4559ae 100644
--- a/pod/perltodo.pod
+++ b/pod/perltodo.pod
@@ -20,17 +20,23 @@ not, but if your patch is incorporated, then we'll add your name to the
F file, which ships in the official distribution. How many other
programming languages offer you 1 line of immortality?
-=head1 The roadmap to 5.10
+=head1 Tasks that only need Perl knowledge
-The roadmap to 5.10 envisages feature based releases, as various items in this
-TODO are completed.
+=head2 Remove duplication of test setup.
-=head2 Needed for the final 5.10.0 release
+Schwern notes, that there's duplication of code - lots and lots of tests have
+some variation on the big block of C<$Is_Foo> checks. We can safely put this
+into a file, change it to build an C<%Is> hash and require it. Maybe just put
+it into F. Throw in the handy tainting subroutines.
-Review perlguts. Significant changes have occured since 5.8, and we can't
-release a new version without making sure these are covered.
+=head2 merge common code in installperl and installman
-=head1 Tasks that only need Perl knowledge
+There are some common subroutines and a common C block in F
+and F. These should probably be merged. It would also be good to
+check for duplication in all the utility scripts supplied in the source
+tarball. It might be good to move them all to a subdirectory, but this would
+require careful checking to find all places that call them, and change those
+correctly.
=head2 common test code for timed bail out
@@ -38,7 +44,7 @@ Write portable self destruct code for tests to stop them burning CPU in
infinite loops. This needs to avoid using alarm, as some of the tests are
testing alarm/sleep or timers.
-=head2 POD -> HTML conversion in the core still sucks
+=head2 POD -E HTML conversion in the core still sucks
Which is crazy given just how simple POD purports to be, and how simple HTML
can be. It's not actually I simple as it sounds, particularly with the
@@ -50,6 +56,19 @@ is needed to improve the cross-linking.
The addition of C and its related modules may make this task
easier to complete.
+=head2 merge checkpods and podchecker
+
+F (and C in the F subdirectory)
+implements a very basic check for pod files, but the errors it discovers
+aren't found by podchecker. Add this check to podchecker, get rid of
+checkpods and have C use podchecker.
+
+=head2 perlmodlib.PL rewrite
+
+Currently perlmodlib.PL needs to be run from a source directory where perl
+has been built, or some modules won't be found, and others will be
+skipped. Make it run from a clean perl source tree (so it's reproducible).
+
=head2 Parallel testing
(This probably impacts much more than the core: also the Test::Harness
@@ -97,6 +116,28 @@ tests that are currently missing.
A full test suite for the B module would be nice.
+=head2 Deparse inlined constants
+
+Code such as this
+
+ use constant PI => 4;
+ warn PI
+
+will currently deparse as
+
+ use constant ('PI', 4);
+ warn 4;
+
+because the tokenizer inlines the value of the constant subroutine C.
+This allows various compile time optimisations, such as constant folding
+and dead code elimination. Where these haven't happened (such as the example
+above) it ought be possible to make B::Deparse work out the name of the
+original constant, because just enough information survives in the symbol
+table to do this. Specifically, the same scalar is used for the constant in
+the optree as is used for the constant subroutine, so by iterating over all
+symbol tables and generating a mapping of SV address to constant name, it
+would be possible to provide B::Deparse with this functionality.
+
=head2 A decent benchmark
C seems impervious to any recent changes made to the perl core. It
@@ -118,6 +159,9 @@ distribution needs to be dual lifed. Anything else can be too. Figure out what
changes would be needed to package that module and its tests up for CPAN, and
do so. Test it with older perl releases, and fix the problems you find.
+To make a minimal perl distribution, it's useful to look at
+F.
+
=head2 Improving C
Investigate whether C could share aggregates properly with
@@ -134,7 +178,7 @@ for example POSIX passes Exporter some very memory hungry data structures.
There is a script F that generates several header files to prefix
all of Perl's symbols in a consistent way, to provide some semblance of
namespace support in C. Functions are declared in F, variables
-in F and F. Quite a few of the functions and variables
+in F. Quite a few of the functions and variables
are conditionally declared there, using C<#ifdef>. However, F
doesn't understand the C macros, so the rules about which symbols are present
when is duplicated in F. Writing things twice is bad, m'kay.
@@ -158,6 +202,8 @@ then C
would be roughly equivalent to:
+
+ do { local $"='|'; /\b(?:P)\b/ }
+
+See L
+for the discussion.
+
=head2 optional optimizer
Make the peephole optimizer optional. Currently it performs two tasks as
@@ -602,15 +775,6 @@ instated.
The old perltodo notes "Look at the "reification" code in C".
-=head2 What hooks would assertions need?
-
-Assertions are in the core, and work. However, assertions needed to be added
-as a core patch, rather than an XS module in ext, or a CPAN module, because
-the core has no hooks in the necessary places. It would be useful to
-investigate what hooks would need to be added to make it possible to provide
-the full assertion support from a CPAN module, so that we aren't constraining
-the imagination of future CPAN authors.
-
=head2 Properly Unicode safe tokeniser and pads.
The tokeniser isn't actually very UTF-8 clean. C