X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=pod%2Fperltodo.pod;h=8626f2a9b5e43adc0d1a538a4054487c1b504e41;hb=749904bf2195f9729fc311a9dd49d33ae8ecad02;hp=a19dfd87ee31a240a555d7f0abcc1f39e6ef200a;hpb=613693f3872d8e1bdd53ae751887e7aa293ce3bd;p=p5sagit%2Fp5-mst-13.2.git

diff --git a/pod/perltodo.pod b/pod/perltodo.pod
index a19dfd8..8626f2a 100644
--- a/pod/perltodo.pod
+++ b/pod/perltodo.pod
@@ -4,683 +4,427 @@ perltodo - Perl TO-DO List
 
 =head1 DESCRIPTION
 
-This is a list of wishes for Perl.  Send updates to
-I<perl5-porters@perl.org>.  If you want to work on any of these
-projects, be sure to check the perl5-porters archives for past ideas,
-flames, and propaganda.  This will save you time and also prevent you
-from implementing something that Larry has already vetoed.  One set
-of archives may be found at:
+This is a list of wishes for Perl. The tasks we think are smaller or easier
+are listed first. Anyone is welcome to work on any of these, but it's a good
+idea to first contact I<perl5-porters@perl.org> to avoid duplication of
+effort. By all means contact a pumpking privately first if you prefer.
+
+Whilst patches to make the list shorter are most welcome, ideas to add to
+the list are also encouraged. Check the perl5-porters archives for past
+ideas, and any discussion about them. One set of archives may be found at:
 
     http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/
 
-=head1 To do during 5.6.x
+What can we offer you in return? Fame, fortune, and everlasting glory? Maybe
+not, but if your patch is incorporated, then we'll add your name to the
+F<AUTHORS> file, which ships in the official distribution. How many other
+programming languages offer you 1 line of immortality?
 
-=head2 Support for I/O disciplines
+=head1 The roadmap to 5.10
 
-C<perlio> provides this, but the interface could be a lot more
-straightforward.
+The roadmap to 5.10 envisages feature based releases, as various items in this
+TODO are completed.
 
-=head2 Autoload bytes.pm
+=head2 Needed for the final 5.10.0 release
 
-When the lexer sees, for instance, C<bytes::length>, it should
-automatically load the C<bytes> pragma.
+Review perlguts. Significant changes have occured since 5.8, and we can't
+release a new version without making sure these are covered.
 
-=head2 Make "\u{XXXX}" et al work
+=head1 Tasks that only need Perl knowledge
 
-Danger, Will Robinson! Discussing the semantics of C<"\x{F00}">,
-C<"\xF00"> and C<"\U{F00}"> on P5P I<will> lead to a long and boring
-flamewar.
+=head2 common test code for timed bail out
 
-=head2 Create a char *sv_pvprintify(sv, STRLEN *lenp, UV flags)
+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.
 
-For displaying PVs with control characters, embedded nulls, and Unicode.
-This would be useful for printing warnings, or data and regex dumping,
-not_a_number(), and so on.
+=head2 POD -> HTML conversion in the core still sucks
 
-Requirements: should handle both byte and UTF8 strings.  isPRINT()
-characters printed as-is, character less than 256 as \xHH, Unicode
-characters as \x{HHH}.  Don't assume ASCII-like, either, get somebody
-on EBCDIC to test the output.
+Which is crazy given just how simple POD purports to be, and how simple HTML
+can be. It's not actually I<as> simple as it sounds, particularly with the
+flexibility POD allows for C<=item>, but it would be good to improve the
+visual appeal of the HTML generated, and to avoid it having any validation
+errors. See also L</make HTML install work>, as the layout of installation tree
+is needed to improve the cross-linking.
 
-Possible options, controlled by the flags:
-- whitespace (other than ' ' of isPRINT()) printed as-is
-- use isPRINT_LC() instead of isPRINT()
-- print control characters like this: "\cA"
-- print control characters like this: "^A"
-- non-PRINTables printed as '.' instead of \xHH
-- use \OOO instead of \xHH
-- use the C/Perl-metacharacters like \n, \t
-- have a maximum length for the produced string (read it from *lenp)
-- append a "..." to the produced string if the maximum length is exceeded
-- really fancy: print unicode characters as \N{...}
+The addition of C<Pod::Simple> and its related modules may make this task
+easier to complete.
 
-NOTE: pv_display(), pv_uni_display(), sv_uni_display() are already
-doing something like the above.
+=head2 Parallel testing
 
-=head2 Overloadable regex assertions
+(This probably impacts much more than the core: also the Test::Harness
+and TAP::* modules on CPAN.)
 
-This may or may not be possible with the current regular expression
-engine. The idea is that, for instance, C<\b> needs to be
-algorithmically computed if you're dealing with Thai text. Hence, the
-B<\b> assertion wants to be overloaded by a function.
+The core regression test suite is getting ever more comprehensive, which has
+the side effect that it takes longer to run. This isn't so good. Investigate
+whether it would be feasible to give the harness script the B<option> of
+running sets of tests in parallel. This would be useful for tests in
+F<t/op/*.t> and F<t/uni/*.t> and maybe some sets of tests in F<lib/>.
 
-=head2 Unicode
+Questions to answer
 
 =over 4
 
-=item *
+=item 1
 
-Allow for long form of the General Category Properties, e.g
-C<\p{IsOpenPunctuation}>, not just the abbreviated form, e.g.
-C<\p{IsPs}>.
+How does screen layout work when you're running more than one test?
 
-=item *
+=item 2
 
-Allow for the metaproperties: C<XID Start>, C<XID Continue>,
-C<NF*_NO>, C<NF*_MAYBE> (require the DerivedCoreProperties and
-DerviceNormalizationProperties files).
+How does the caller of test specify how many tests to run in parallel?
 
-There are also multiple value properties still unimplemented:
-C<Numeric Type>, C<East Asian Width>.
+=item 3
 
-=item *
-
-    Case Mappings? http://www.unicode.org/unicode/reports/tr21/
-
-Mostly implemented (all of 1:1, 1:N, N:1), only the "final sigma"
-and locale-specific rules of SpecCase are not implemented.
-
-=item *
-
-UTF-8 identifier names should probably be canonicalized: NFC?
-
-=item *
-
-UTF-8 in package names and sub names?  The first is problematic
-because of the mapping to pathnames, ditto for the second one if
-one does autosplitting, for example.  Some of this works already
-in 5.8.0, but essentially it is unsupported.  Constructs to consider,
-at the very least:
-
-	use utf8;
-	package UnicodePackage;
-	sub new { bless {}, shift };
-	sub UnicodeMethod1 { ... $_[0]->UnicodeMethod2(...) ... }
-	sub UnicodeMethod2 { ... } # in here caller(0) should contain Unicode
-	...
-	package main;
-	my $x = UnicodePackage->new;
-	print ref $x, "\n";  # should be Unicode
-	$x->UnicodeMethod1(...);
-	my $y = UnicodeMethod3 UnicodePackage ...;
-
-In the above all I<UnicodeXxx> contain (identifier-worthy) characters
-beyond the code point 255, for example 256.  Wherever package/class or
-subroutine names can be returned needs to be checked for Unicodeness.
+How do setup/teardown tests identify themselves?
 
 =back
 
-See L<perlunicode/UNICODE REGULAR EXPRESSION SUPPORT LEVEL> for what's
-there and what's missing.  Almost all of Levels 2 and 3 is missing,
-and as of 5.8.0 not even all of Level 1 is there.
-They have some tricks Perl doesn't yet implement, such as character
-class subtraction.
-
-	http://www.unicode.org/unicode/reports/tr18/
-
-=head2 Work out exit/die semantics for threads
-
-There are some suggestions to use for example something like this:
-default to "(thread exiting first will) wait for the other threads
-until up to 60 seconds".  Other possibilities:
-
-    use threads wait => 0;
-
-Do not wait.
-
-    use threads wait_for => 10;
-
-Wait up to 10 seconds.
-
-    use threads wait_for => -1;
-
-Wait for ever.
-
-http://archive.develooper.com/perl5-porters@perl.org/msg79618.html
-
-=head2 Better support for nonpreemptive threading systems like GNU pth
-
-To better support nonpreemptive threading systems, perhaps some of the
-blocking functions internally in Perl should do a yield() before a
-blocking call.  (Now certain threads tests ({basic,list,thread.t})
-simply do a yield() before they sleep() to give nonpreemptive thread
-implementations a chance).
-
-In some cases, like the GNU pth, which has replacement functions that
-are nonblocking (pth_select instead of select), maybe Perl should be
-using them instead when built for threading.
-
-=head2 Typed lexicals for compiler
-
-=head2 Compiler workarounds for Win32
-
-=head2 AUTOLOADing in the compiler
-
-=head2 Fixing comppadlist when compiling
-
-=head2 Cleaning up exported namespace
-
-=head2 Complete signal handling
-
-Add C<PERL_ASYNC_CHECK> to opcodes which loop; replace C<sigsetjmp> with
-C<sigjmp>; check C<wait> for signal safety.
-
-=head2 Out-of-source builds
-
-This was done for 5.6.0, but needs reworking for 5.7.x
-
-=head2 POSIX realtime support
-
-POSIX 1003.1 1996 Edition support--realtime stuff: POSIX semaphores,
-message queues, shared memory, realtime clocks, timers, signals (the
-metaconfig units mostly already exist for these)
-
-=head2 UNIX98 support
-
-Reader-writer locks, realtime/asynchronous IO
-
-=head2 IPv6 Support
-
-There are non-core modules, such as C<Socket6>, but these will need
-integrating when IPv6 actually starts to really happen.  See RFC 2292
-and RFC 2553.
-
-=head2 Long double conversion
-
-Floating point formatting is still causing some weird test failures.
-
-=head2 Locales
-
-Locales and Unicode interact with each other in unpleasant ways.
-One possible solution would be to adopt/support ICU:
-
-	http://oss.software.ibm.com/developerworks/opensource/icu/project/
-
-=head2 Arithmetic on non-Arabic numerals
-
-C<[1234567890]> aren't the only numerals any more.
-
-=head2 POSIX Unicode character classes
-
-(C<[=a=]> for equivalence classes, C<[.ch.]> for collation.)
-These are dependent on Unicode normalization and collation.
-
-=head2 Factoring out common suffices/prefices in regexps (trie optimization)
-
-Currently, the user has to optimize C<foo|far> and C<foo|goo> into
-C<f(?:oo|ar)> and C<[fg]oo> by hand; this could be done automatically.
-
-=head2 Security audit shipped utilities
-
-All the code we ship with Perl needs to be sensible about temporary file
-handling, locking, input validation, and so on.
-
-=head2 Sort out the uid-setting mess
-
-Currently there are several problems with the setting of uids ($<, $>
-for the real and effective uids).  Firstly, what exactly setuid() call
-gets invoked in which platform is simply a big mess that needs to be
-untangled.  Secondly, the effects are apparently not standard across
-platforms, (if you first set $< and then $>, or vice versa, being
-uid == euid == zero, or just euid == zero, or as a normal user, what are
-the results?).  The test suite not (usually) being run as root means
-that these things do not get much testing.  Thirdly, there's quite
-often a third uid called saved uid, and Perl has no knowledge of that
-feature in any way.  (If one has the saved uid of zero, one can get
-back any real and effective uids.)  As an example, to change also the
-saved uid, one needs to set the real and effective uids B<twice>-- in
-most systems, that is: in HP-UX that doesn't seem to work.
-
-=head2 Custom opcodes
-
-Have a way to introduce user-defined opcodes without the subroutine call
-overhead of an XSUB; the user should be able to create PP code. Simon
-Cozens has some ideas on this.
-
-=head2 DLL Versioning
-
-Windows needs a way to know what version of an XS or C<libperl> DLL it's
-loading.
-
-=head2 Introduce @( and @)
-
-C<$(> may return "foo bar baz". Unfortunately, since groups can
-theoretically have spaces in their names, this could be one, two or
-three groups.
-
-=head2 Floating point handling
-
-C<NaN> and C<inf> support is particularly troublesome.
-(fp_classify(), fp_class(), fp_class_d(), class(), isinf(),
-isfinite(), finite(), isnormal(), unordered(), <ieeefp.h>,
-<fp_class.h> (there are metaconfig units for all these) (I think),
-fp_setmask(), fp_getmask(), fp_setround(), fp_getround()
-(no metaconfig units yet for these).  Don't forget finitel(), fp_classl(),
-fp_class_l(), (yes, both do, unfortunately, exist), and unorderedl().)
-
-As of Perl 5.6.1, there is a Perl macro, Perl_isnan().
-
-=head2 IV/UV preservation
-
-Nicholas Clark has done a lot of work on this, but work is continuing.
-C<+>, C<-> and C<*> work, but guards need to be in place for C<%>, C</>,
-C<&>, C<oct>, C<hex> and C<pack>.
-
-=head2 Replace pod2html with something using Pod::Parser
-
-The CPAN module C<Marek::Pod::Html> may be a more suitable basis for a
-C<pod2html> converter; the current one duplicates the functionality
-abstracted in C<Pod::Parser>, which makes updating the POD language
-difficult.
-
-=head2 Automate module testing on CPAN
-
-When a new Perl is being beta tested, porters have to manually grab
-their favourite CPAN modules and test them - this should be done
-automatically.
-
-=head2 sendmsg and recvmsg
-
-We have all the other BSD socket functions but these. There are
-metaconfig units for these functions which can be added. To avoid these
-being new opcodes, a solution similar to the way C<sockatmark> was added
-would be preferable. (Autoload the C<IO::whatever> module.)
-
-=head2 Rewrite perlre documentation
-
-The new-style patterns need full documentation, and the whole document
-needs to be a lot clearer.
-
-=head2 Convert example code to IO::Handle filehandles
-
-=head2 Document Win32 choices
-
-=head2 Check new modules
-
-=head2 Make roffitall find pods and libs itself
-
-Simon Cozens has done some work on this but it needs a rethink.
-
-=head1 To do at some point
-
-These are ideas that have been regularly tossed around, that most
-people believe should be done maybe during 5.8.x
-
-=head2 Remove regular expression recursion
-
-Because the regular expression engine is recursive, badly designed
-expressions can lead to lots of recursion filling up the stack. Ilya
-claims that it is easy to convert the engine to being iterative, but
-this has still not yet been done. There may be a regular expression
-engine hit squad meeting at TPC5.
-
-=head2 Memory leaks after failed eval
-
-Perl will leak memory if you C<eval "hlagh hlagh hlagh hlagh">. This is
-partially because it attempts to build up an op tree for that code and
-doesn't properly free it. The same goes for non-syntactically-correct
-regular expressions. Hugo looked into this, but decided it needed a
-mark-and-sweep GC implementation. 
-
-Alan notes that: The basic idea was to extend the parser token stack
-(C<YYSTYPE>) to include a type field so we knew what sort of thing each
-element of the stack was.  The F<perly.c> code would then have to be
-postprocessed to record the type of each entry on the stack as it was
-created, and the parser patched so that it could unroll the stack
-properly on error.
-
-This is possible to do, but would be pretty messy to implement, as it
-would rely on even more sed hackery in F<perly.fixer>.
-
-=head2 bitfields in pack
-
-=head2 Cross compilation
-
-Make Perl buildable with a cross-compiler. This will play havoc with
-Configure, which needs to know how the target system will respond to
-its tests; maybe C<microperl> will be a good starting point here.
-(Indeed, Bart Schuller reports that he compiled up C<microperl> for
-the Agenda PDA and it works fine.)  A really big spanner in the works
-is the bootstrapping build process of Perl: if the filesystem the
-target systems sees is not the same what the build host sees, various
-input, output, and (Perl) library files need to be copied back and forth.
-
-As of 5.8.0 Configure mostly works for cross-compilation
-(used successfully for iPAQ Linux), miniperl gets built,
-but then building DynaLoader (and other extensions) fails
-since MakeMaker knows nothing of cross-compilation.
-(See INSTALL/Cross-compilation for the state of things.)
-
-=head2 Perl preprocessor / macros
-
-Source filters help with this, but do not get us all the way. For
-instance, it should be possible to implement the C<??> operator somehow;
-source filters don't (quite) cut it.
-
-=head2 Perl lexer in Perl
-
-Damian Conway is planning to work on this, but it hasn't happened yet.
-
-=head2 Using POSIX calls internally
+Pugs already does parallel testing - can their approach be re-used?
 
-When faced with a BSD vs. SysV -style interface to some library or
-system function, perl's roots show in that it typically prefers the BSD
-interface (but falls back to the SysV one).  One example is getpgrp().
-Other examples include C<memcpy> vs. C<bcopy>.  There are others, mostly in
-F<pp_sys.c>.
+=head2 Make Schwern poorer
 
-Mostly, this item is a suggestion for which way to start a journey into
-an C<#ifdef> forest.  It is not primarily a suggestion to eliminate any of
-the C<#ifdef> forests.
+We should have tests for everything. When all the core's modules are tested,
+Schwern has promised to donate to $500 to TPF. We may need volunteers to
+hold him upside down and shake vigorously in order to actually extract the
+cash.
 
-POSIX calls are perhaps more likely to be portable to unexpected
-architectures. They are also perhaps more likely to be actively
-maintained by a current vendor.  They are also perhaps more likely to be
-available in thread-safe versions, if appropriate.
+=head2 Improve the coverage of the core tests
 
-=head2 -i rename file when changed
+Use Devel::Cover to ascertain the core modules's test coverage, then add
+tests that are currently missing.
 
-It's only necessary to rename a file when inplace editing when the file
-has changed. Detecting a change is perhaps the difficult bit.
+=head2 test B
 
-=head2 All ARGV input should act like E<lt>E<gt>
+A full test suite for the B module would be nice.
 
-eg C<read(ARGV, ...)> doesn't currently read across multiple files.
+=head2 A decent benchmark
 
-=head2 Support for rerunning debugger
+C<perlbench> seems impervious to any recent changes made to the perl core. It
+would be useful to have a reasonable general benchmarking suite that roughly
+represented what current perl programs do, and measurably reported whether
+tweaks to the core improve, degrade or don't really affect performance, to
+guide people attempting to optimise the guts of perl. Gisle would welcome
+new tests for perlbench.
 
-There should be a way of restarting the debugger on demand.
+=head2 fix tainting bugs
 
-=head2 Test Suite for the Debugger
+Fix the bugs revealed by running the test suite with the C<-t> switch (via
+C<make test.taintwarn>).
 
-The debugger is a complex piece of software and fixing something
-here may inadvertently break something else over there.  To tame
-this chaotic behaviour, a test suite is necessary. 
+=head2 Dual life everything
 
-=head2 my sub foo { }
+As part of the "dists" plan, anything that doesn't belong in the smallest perl
+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.
 
-The basic principle is sound, but there are problems with the semantics
-of self-referential and mutually referential lexical subs: how to
-declare the subs?
+=head2 Improving C<threads::shared>
 
-=head2 One-pass global destruction
+Investigate whether C<threads::shared> could share aggregates properly with
+only Perl level changes to shared.pm
 
-Sweeping away all the allocated memory in one go is a laudable goal, but
-it's difficult and in most cases, it's easier to let the memory get
-freed by exiting.
+=head2 POSIX memory footprint
 
-=head2 Rewrite regexp parser
+Ilya observed that use POSIX; eats memory like there's no tomorrow, and at
+various times worked to cut it down. There is probably still fat to cut out -
+for example POSIX passes Exporter some very memory hungry data structures.
 
-There has been talk recently of rewriting the regular expression parser
-to produce an optree instead of a chain of opcodes; it's unclear whether
-or not this would be a win. 
+=head2 embed.pl/makedef.pl
 
-=head2 Cache recently used regexps
+There is a script F<embed.pl> 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<C>. Functions are declared in F<embed.fnc>, variables
+in F<interpvar.h> and F<thrdvar.h>. Quite a few of the functions and variables
+are conditionally declared there, using C<#ifdef>. However, F<embed.pl>
+doesn't understand the C macros, so the rules about which symbols are present
+when is duplicated in F<makedef.pl>. Writing things twice is bad, m'kay.
+It would be good to teach C<embed.pl> to understand the conditional
+compilation, and hence remove the duplication, and the mistakes it has caused.
 
-This is to speed up 
+=head1 Tasks that need a little sysadmin-type knowledge
 
-    for my $re (@regexps) {
-        $matched++ if /$re/
-    }
+Or if you prefer, tasks that you would learn from, and broaden your skills
+base...
 
-C<qr//> already gives us a way of saving compiled regexps, but it should
-be done automatically.
+=head2 make HTML install work
 
-=head2 Cross-compilation support
+There is an C<installhtml> target in the Makefile. It's marked as
+"experimental". It would be good to get this tested, make it work reliably, and
+remove the "experimental" tag. This would include
 
-Bart Schuller reports that using C<microperl> and a cross-compiler, he
-got Perl working on the Agenda PDA. However, one cannot build a full
-Perl because Configure needs to get the results for the target platform,
-for the host.
-
-=head2 Bit-shifting bitvectors
-
-Given:
-
-    vec($v, 1000, 1) = 1;
-
-One should be able to do
-
-    $v <<= 1;
-
-and have the 999'th bit set.
-
-Currently if you try with shift bitvectors you shift the NV/UV, instead
-of the bits in the PV.  Not very logical.
-
-=head2 debugger pragma
-
-The debugger is implemented in Perl in F<perl5db.pl>; turning it into a
-pragma should be easy, but making it work lexically might be more
-difficult. Fiddling with C<$^P> would be necessary.
-
-=head2 use less pragma
-
-Identify areas where speed/memory tradeoffs can be made and have a hint
-to switch between them.
-
-=head2 switch structures
-
-Although we have C<Switch.pm> in core, Larry points to the dormant
-C<nswitch> and C<cswitch> ops in F<pp.c>; using these opcodes would be
-much faster.
-
-=head2 Cache eval tree
-
-=head2 rcatmaybe
-
-=head2 Shrink opcode tables
-
-=head2 Optimize away @_
-
-Look at the "reification" code in C<av.c>
-
-=head2 Prototypes versus indirect objects
-
-Currently, indirect object syntax bypasses prototype checks.
-
-=head2 Install HTML
-
-HTML versions of the documentation need to be installed by default; a
-call to C<installhtml> from C<installperl> may be all that's necessary.
-
-=head2 Prototype method calls
-
-=head2 Return context prototype declarations
-
-=head2 magic_setisa
-
-=head2 Garbage collection
-
-There have been persistent mumblings about putting a mark-and-sweep
-garbage detector into Perl; Alan Burlison has some ideas about this.
-
-=head2 IO tutorial
-
-Mark-Jason Dominus has the beginnings of one of these.
-
-=head2 Rewrite perldoc
-
-There are a few suggestions for what to do with C<perldoc>: maybe a
-full-text search, an index function, locating pages on a particular
-high-level subject, and so on.
-
-=head2 Install .3p manpages
-
-This is a bone of contention; we can create C<.3p> manpages for each
-built-in function, but should we install them by default? Tcl does this,
-and it clutters up C<apropos>.
-
-=head2 Unicode tutorial
+=over 4
 
-Simon Cozens promises to do this before he gets old.
+=item 1
 
-=head2 Update POSIX.pm for 1003.1-2
+Checking that cross linking between various parts of the documentation works.
+In particular that links work between the modules (files with POD in F<lib/>)
+and the core documentation (files in F<pod/>)
 
-=head2 Retargetable installation
+=item 2
 
-Allow C<@INC> to be changed after Perl is built.
+Work out how to split C<perlfunc> into chunks, preferably one per function
+group, preferably with general case code that could be used elsewhere.
+Challenges here are correctly identifying the groups of functions that go
+together, and making the right named external cross-links point to the right
+page. Things to be aware of are C<-X>, groups such as C<getpwnam> to
+C<endservent>, two or more C<=items> giving the different parameter lists, such
+as
 
-=head2 POSIX emulation on non-POSIX systems
+    =item substr EXPR,OFFSET,LENGTH,REPLACEMENT
+    =item substr EXPR,OFFSET,LENGTH
+    =item substr EXPR,OFFSET
 
-Make C<POSIX.pm> behave as POSIXly as possible everywhere, meaning we
-have to implement POSIX equivalents for some functions if necessary.
+and different parameter lists having different meanings. (eg C<select>)
 
-=head2 Rename Win32 headers
+=back
 
-=head2 Finish off lvalue functions
+=head2 compressed man pages
 
-They don't work in the debugger, and they don't work for list or hash
-slices.
+Be able to install them. This would probably need a configure test to see how
+the system does compressed man pages (same directory/different directory?
+same filename/different filename), as well as tweaking the F<installman> script
+to compress as necessary.
 
-=head2 Update sprintf documentation
+=head2 Add a code coverage target to the Makefile
 
-Hugo van der Sanden plans to look at this.
+Make it easy for anyone to run Devel::Cover on the core's tests. The steps
+to do this manually are roughly
 
-=head2 Use fchown/fchmod internally
+=over 4
 
-This has been done in places, but needs a thorough code review.
-Also fchdir is available in some platforms.
+=item *
 
-=head2 Make v-strings overloaded objects
+do a normal C<Configure>, but include Devel::Cover as a module to install
+(see F<INSTALL> for how to do this)
 
-Instead of having to guess whether a string is a v-string and thus
-needs to be displayed with %vd, make v-strings (readonly) objects
-(class "vstring"?) with a stringify overload.
+=item *
 
-=head2 Allow restricted hash assignment
+    make perl
 
-Currently you're not allowed to assign to a restricted hash at all,
-even with the same keys.
+=item *
 
-    %restricted = (foo => 42);  # error
+    cd t; HARNESS_PERL_SWITCHES=-MDevel::Cover ./perl -I../lib harness
 
-This should be allowed if the new keyset is a subset of the old
-keyset.  May require more extra code than we'd like in pp_aassign.
+=item *
 
-=head2 Should overload be inheritable?
+Process the resulting Devel::Cover database
 
-Should overload be 'contagious' through @ISA so that derived classes
-would inherit their base classes' overload definitions?  What to do
-in case of overload conflicts?
+=back
 
-=head2 Taint rethink
+This just give you the coverage of the F<.pm>s. To also get the C level
+coverage you need to
 
-Should taint be stopped from affecting control flow, if ($tainted)?
-Should tainted symbolic method calls and subref calls be stopped?
-(Look at Ruby's $SAFE levels for inspiration?)
+=over 4
 
-=head1 Vague ideas
+=item *
 
-Ideas which have been discussed, and which may or may not happen.
+Additionally tell C<Configure> to use the appropriate C compiler flags for
+C<gcov>
 
-=head2 ref() in list context
+=item *
 
-It's unclear what this should do or how to do it without breaking old
-code.
+    make perl.gcov
 
-=head2 Make tr/// return histogram of characters in list context
+(instead of C<make perl>)
 
-There is a patch for this, but it may require Unicodification.
+=item *
 
-=head2 Compile to real threaded code
+After running the tests run C<gcov> to generate all the F<.gcov> files.
+(Including down in the subdirectories of F<ext/>
 
-=head2 Structured types
+=item *
 
-=head2 Modifiable $1 et al.
+(From the top level perl directory) run C<gcov2perl> on all the C<.gcov> files
+to get their stats into the cover_db directory.
 
-    ($x = "elephant") =~ /e(ph)/;
-    $1 = "g"; # $x = "elegant"
+=item *
 
-What happens if there are multiple (nested?) brackets? What if the
-string changes between the match and the assignment?
+Then process the Devel::Cover database
 
-=head2 Procedural interfaces for IO::*, etc.
+=back
 
-Some core modules have been accused of being overly-OO. Adding
-procedural interfaces could demystify them.
+It would be good to add a single switch to C<Configure> to specify that you
+wanted to perform perl level coverage, and another to specify C level
+coverage, and have C<Configure> and the F<Makefile> do all the right things
+automatically.
 
-=head2 RPC modules
+=head2 Make Config.pm cope with differences between built and installed perl
+
+Quite often vendors ship a perl binary compiled with their (pay-for)
+compilers.  People install a free compiler, such as gcc. To work out how to
+build extensions, Perl interrogates C<%Config>, so in this situation
+C<%Config> describes compilers that aren't there, and extension building
+fails. This forces people into choosing between re-compiling perl themselves
+using the compiler they have, or only using modules that the vendor ships.
+
+It would be good to find a way teach C<Config.pm> about the installation setup,
+possibly involving probing at install time or later, so that the C<%Config> in
+a binary distribution better describes the installed machine, when the
+installed machine differs from the build machine in some significant way.
+
+=head2 linker specification files
+
+Some platforms mandate that you provide a list of a shared library's external
+symbols to the linker, so the core already has the infrastructure in place to
+do this for generating shared perl libraries. My understanding is that the
+GNU toolchain can accept an optional linker specification file, and restrict
+visibility just to symbols declared in that file. It would be good to extend
+F<makedef.pl> to support this format, and to provide a means within
+C<Configure> to enable it. This would allow Unix users to test that the
+export list is correct, and to build a perl that does not pollute the global
+namespace with private symbols.
+
+=head2 Cross-compile support
+
+Currently C<Configure> understands C<-Dusecrosscompile> option. This option
+arranges for building C<miniperl> for TARGET machine, so this C<miniperl> is
+assumed then to be copied to TARGET machine and used as a replacement of full
+C<perl> executable.
+
+This could be done little differently. Namely C<miniperl> should be built for
+HOST and then full C<perl> with extensions should be compiled for TARGET.
+This, however, might require extra trickery for %Config: we have one config
+first for HOST and then another for TARGET.
+
+=head1 Tasks that need a little C knowledge
+
+These tasks would need a little C knowledge, but don't need any specific
+background or experience with XS, or how the Perl interpreter works
+
+=head2 Make it clear from -v if this is the exact official release
+
+Currently perl from C<p4>/C<rsync> ships with a F<patchlevel.h> file that
+usually defines one local patch, of the form "MAINT12345" or "RC1". The output
+of perl -v doesn't report that a perl isn't an official release, and this
+information can get lost in bugs reports. Because of this, the minor version
+isn't bumped up until RC time, to minimise the possibility of versions of perl
+escaping that believe themselves to be newer than they actually are.
+
+It would be useful to find an elegant way to have the "this is an interim
+maintenance release" or "this is a release candidate" in the terse -v output,
+and have it so that it's easy for the pumpking to remove this just as the
+release tarball is rolled up. This way the version pulled out of rsync would
+always say "I'm a development release" and it would be safe to bump the
+reported minor version as soon as a release ships, which would aid perl
+developers.
+
+This task is really about thinking of an elegant way to arrange the C source
+such that it's trivial for the Pumpking to flag "this is an official release"
+when making a tarball, yet leave the default source saying "I'm not the
+official release".
+
+=head2 Ordering of "global" variables.
+
+F<thrdvar.h> and F<intrpvarh> define the "global" variables that need to be
+per-thread under ithreads, where the variables are actually elements in a
+structure. As C dictates, the variables must be laid out in order of
+declaration. There is a comment
+C</* Important ones in the first cache line (if alignment is done right) */>
+which implies that at some point in the past the ordering was carefully chosen
+(at least in part). However, it's clear that the ordering is less than perfect,
+as currently there are things such as 7 C<bool>s in a row, then something
+typically requiring 4 byte alignment, and then an odd C<bool> later on.
+(C<bool>s are typically defined as C<char>s). So it would be good for someone
+to review the ordering of the variables, to see how much alignment padding can
+be removed.
 
-=head2 Attach/detach debugger from running program
+It's also worth checking that all variables are actually used. Perl 5.8.0
+shipped with C<PL_nrs> still defined in F<thrdvar.h>, despite it being unused
+since a change over a year earlier. Had this been spotted before release, it
+could have been removed, but now it has to remain in the 5.8.x releases to
+keep the structure the same size, to retain binary compatibility.
 
-With C<gdb>, you can attach the debugger to a running program if you
-pass the process ID. It would be good to do this with the Perl debugger
-on a running Perl program, although I'm not sure how it would be done.
+It's probably worth checking if all need to be the types they are. For example
 
-=head2 GUI::Native
+    PERLVAR(Ierror_count, I32)	/* how many errors so far, max 10 */
 
-A non-core module that would use "native" GUI to create graphical
-applications.
+might work as well if stored in a signed (or unsigned) 8 bit value, if the
+comment is accurate. C<PL_multi_open> and C<PL_multi_close> can probably
+become C<char>s. Finding variables to downsize coupled with rearrangement
+could shrink the interpreter structure; a size saving which is multiplied by
+the number of threads running.
 
-=head2 foreach(reverse ...)
+=head2 Profile Perl - am I hot or not?
 
-Currently
+The Perl source code is stable enough that it makes sense to profile it,
+identify and optimise the hotspots. It would be good to measure the
+performance of the Perl interpreter using free tools such as cachegrind,
+gprof, and dtrace, and work to reduce the bottlenecks they reveal.
+
+As part of this, the idea of F<pp_hot.c> is that it contains the I<hot> ops,
+the ops that are most commonly used. The idea is that by grouping them, their
+object code will be adjacent in the executable, so they have a greater chance
+of already being in the CPU cache (or swapped in) due to being near another op
+already in use.
 
-    foreach (reverse @_) { ... }
+Except that it's not clear if these really are the most commonly used ops. So
+as part of exercising your skills with coverage and profiling tools you might
+want to determine what ops I<really> are the most commonly used. And in turn
+suggest evictions and promotions to achieve a better F<pp_hot.c>.
 
-puts C<@_> on the stack, reverses it putting the reversed version on the
-stack, then iterates forwards. Instead, it could be special-cased to put
-C<@_> on the stack then iterate backwards.
+=head2 Allocate OPs from arenas
 
-=head2 Constant function cache
+Currently all new OP structures are individually malloc()ed and free()d.
+All C<malloc> implementations have space overheads, and are now as fast as
+custom allocates so it would both use less memory and less CPU to allocate
+the various OP structures from arenas. The SV arena code can probably be
+re-used for this.
 
-=head2 Approximate regular expression matching
+=head2 Improve win32/wince.c
 
-=head1 Ongoing
+Currently, numerous functions look virtually, if not completely,
+identical in both C<win32/wince.c> and C<win32/win32.c> files, which can't
+be good.
 
-These items B<always> need doing:
+=head2 Use secure CRT functions when building with VC8 on Win32
 
-=head2 Update guts documentation
+Visual C++ 2005 (VC++ 8.x) deprecated a number of CRT functions on the basis
+that they were "unsafe" and introduced differently named secure versions of
+them as replacements, e.g. instead of writing
 
-Simon Cozens tries to do this when possible, and contributions to the
-C<perlapi> documentation is welcome.
+    FILE* f = fopen(__FILE__, "r");
 
-=head2 Add more tests
+one should now write
 
-Michael Schwern will donate $500 to Yet Another Society when all core
-modules have tests.
+    FILE* f;
+    errno_t err = fopen_s(&f, __FILE__, "r"); 
 
-=head2 Update auxiliary tools
+Currently, the warnings about these deprecations have been disabled by adding
+-D_CRT_SECURE_NO_DEPRECATE to the CFLAGS. It would be nice to remove that
+warning suppressant and actually make use of the new secure CRT functions.
 
-The code we ship with Perl should look like good Perl 5.
+There is also a similar issue with POSIX CRT function names like fileno having
+been deprecated in favour of ISO C++ conformant names like _fileno. These
+warnings are also currently suppressed with the compiler option /wd4996. It
+might be nice to do as Microsoft suggest here too, although, unlike the secure
+functions issue, there is presumably little or no benefit in this case.
 
-=head2 Create debugging macros
+=head1 Tasks that need a knowledge of XS
 
-Debugging macros (like printsv, dump) can make debugging perl inside a
-C debugger much easier.  A good set for gdb comes with mod_perl.
-Something similar should be distributed with perl.
+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.
 
-The proper way to do this is to use and extend Devel::DebugInit.
-Devel::DebugInit also needs to be extended to support threads.
+=head2 shrink C<PVBM>s
 
-See p5p archives for late May/early June 2001 for a recent discussion
-on this topic.
+By removing unused elements and careful re-ordering, the structures for C<AV>s,
+C<HV>s, C<CV>s and C<GV>s have recently been shrunk considerably. C<PVIO>s
+probably aren't worth it, as typical programs don't use more than 8, and
+(at least) C<Filter::Util::Call> uses C<SvPVX>/C<SvCUR>/C<SvLEN> on a C<PVIO>,
+so it would mean code changes to modules on CPAN. C<PVBM>s might have some
+savings to win.
 
-=head2 truncate to the people
+=head2 autovivification
 
-One can emulate ftruncate() using F_FREESP and F_CHSIZ fcntls
-(see the UNIX FAQ for details).  This needs to go somewhere near
-pp_sys.c:pp_truncate().
+Make all autovivification consistent w.r.t LVALUE/RVALUE and strict/no strict;
 
-One can emulate truncate() easily if one has ftruncate().
-This emulation should also go near pp_sys.pp_truncate().
+This task is incremental - even a little bit of work on it will help.
 
 =head2 Unicode in Filenames
 
 chdir, chmod, chown, chroot, exec, glob, link, lstat, mkdir, open,
 opendir, qx, readdir, readlink, rename, rmdir, stat, symlink, sysopen,
-system, truncate, unlink, utime.  All these could potentially accept
+system, truncate, unlink, utime, -X.  All these could potentially accept
 Unicode filenames either as input or output (and in the case of system
 and qx Unicode in general, as input or output to/from the shell).
 Whether a filesystem - an operating system pair understands Unicode in
@@ -695,276 +439,206 @@ and so on, varies.  Finding the right level of interfacing to Perl
 requires some thought.  Remember that an OS does not implicate a
 filesystem.
 
-Note that in Windows the -C command line flag already does quite
-a bit of the above (but even there the support is not complete:
-for example the exec/spawn are not Unicode-aware) by turning on
-the so-called "wide API support". 
-
-=head1 Recently done things
-
-These are things which have been on the todo lists in previous releases
-but have recently been completed.
-
-=head2 Alternative RE syntax module
-
-The C<Regexp::English> module, available from the CPAN, provides this:
-
-    my $re = Regexp::English
-    -> start_of_line
-    -> literal('Flippers')
-    -> literal(':')
-    -> optional
-        -> whitespace_char
-    -> end
-    -> remember
-        -> multiple
-            -> digit;
-
-    /$re/;
-
-=head2 Safe signal handling
-
-A new signal model went into 5.7.1 without much fanfare. Operations and
-C<malloc>s are no longer interrupted by signals, which are handled
-between opcodes. This means that C<PERL_ASYNC_CHECK> now actually does
-something. However, there are still a few things that need to be done.
-
-=head2 Tie Modules
-
-Modules which implement arrays in terms of strings, substrings or files
-can be found on the CPAN.
-
-=head2 gettimeofday
-
-C<Time::HiRes> has been integrated into the core.
-
-=head2 setitimer and getimiter
-
-Adding C<Time::HiRes> got us this too.
-
-=head2 Testing __DIE__ hook
-
-Tests have been added.
-
-=head2 CPP equivalent in Perl
-
-A C Yardley will probably have done this by the time you can read this.
-This allows for a generalization of the C constant detection used in
-building C<Errno.pm>.
-
-=head2 Explicit switch statements
-
-C<Switch.pm> has been integrated into the core to give you all manner of
-C<switch...case> semantics.
-
-=head2 autocroak
+(The Windows -C command flag "wide API support" has been at least
+temporarily retired in 5.8.1, and the -C has been repurposed, see
+L<perlrun>.)
 
-This is C<Fatal.pm>.
+=head2 Unicode in %ENV
 
-=head2 UTF/EBCDIC
+Currently the %ENV entries are always byte strings.
 
-Nick Ing-Simmons has made UTF-EBCDIC (UTR13) work with Perl.
+=head2 use less 'memory'
 
-    EBCDIC?        http://www.unicode.org/unicode/reports/tr16/
+Investigate trade offs to switch out perl's choices on memory usage.
+Particularly perl should be able to give memory back.
 
-=head2 UTF Regexes
+This task is incremental - even a little bit of work on it will help.
 
-Although there are probably some small bugs to be rooted out, Jarkko
-Hietaniemi has made regular expressions polymorphic between bytes and
-characters.
+=head2 Re-implement C<:unique> in a way that is actually thread-safe
 
-=head2 perlcc to produce executable
+The old implementation made bad assumptions on several levels. A good 90%
+solution might be just to make C<:unique> work to share the string buffer
+of SvPVs. That way large constant strings can be shared between ithreads,
+such as the configuration information in F<Config>.
 
-C<perlcc> was recently rewritten, and can now produce standalone
-executables.
+=head2 Make tainting consistent
 
-=head2 END blocks saved in compiled output
+Tainting would be easier to use if it didn't take documented shortcuts and
+allow taint to "leak" everywhere within an expression.
 
-=head2 Secure temporary file module
+=head2 readpipe(LIST)
 
-Tim Jenness' C<File::Temp> is now in core.
+system() accepts a LIST syntax (and a PROGRAM LIST syntax) to avoid
+running a shell. readpipe() (the function behind qx//) could be similarly
+extended.
 
-=head2 Integrate Time::HiRes
+=head2 strcat(), strcpy(), strncat(), strncpy(), sprintf(), vsprintf()
 
-This module is now part of core.
+Maybe create a utility that checks after each libperl.a creation that
+none of the above (nor sprintf(), vsprintf(), or *SHUDDER* gets())
+ever creep back to libperl.a.
 
-=head2 Turn Cwd into XS
+  nm libperl.a | ./miniperl -alne '$o = $F[0] if /:$/; print "$o $F[1]" if $F[0] eq "U" && $F[1] =~ /^(?:strn?c(?:at|py)|v?sprintf|gets)$/'
 
-Benjamin Sugars has done this.
+Note, of course, that this will only tell whether B<your> platform
+is using those naughty interfaces.
 
-=head2 Mmap for input
+=head2 Audit the code for destruction ordering assumptions
 
-Nick Ing-Simmons' C<perlio> supports an C<mmap> IO method.
+Change 25773 notes
 
-=head2 Byte to/from UTF8 and UTF8 to/from local conversion
+    /* Need to check SvMAGICAL, as during global destruction it may be that
+       AvARYLEN(av) has been freed before av, and hence the SvANY() pointer
+       is now part of the linked list of SV heads, rather than pointing to
+       the original body.  */
+    /* FIXME - audit the code for other bugs like this one.  */
 
-C<Encode> provides this.
+adding the C<SvMAGICAL> check to
 
-=head2 Add sockatmark support
+    if (AvARYLEN(av) && SvMAGICAL(AvARYLEN(av))) {
+        MAGIC *mg = mg_find (AvARYLEN(av), PERL_MAGIC_arylen);
 
-Added in 5.7.1
+Go through the core and look for similar assumptions that SVs have particular
+types, as all bets are off during global destruction.
 
-=head2 Mailing list archives
+=head2 Extend PerlIO and PerlIO::Scalar
 
-http://lists.perl.org/ , http://archive.develooper.com/
+PerlIO::Scalar doesn't know how to truncate().  Implementing this
+would require extending the PerlIO vtable.
 
-=head2 Bug tracking
+Similarly the PerlIO vtable doesn't know about formats (write()), or
+about stat(), or chmod()/chown(), utime(), or flock().
 
-Richard Foley has written the bug tracking system at http://bugs.perl.org/
+(For PerlIO::Scalar it's hard to see what e.g. mode bits or ownership
+would mean.)
 
-=head2 Integrate MacPerl
+PerlIO doesn't do directories or symlinks, either: mkdir(), rmdir(),
+opendir(), closedir(), seekdir(), rewinddir(), glob(); symlink(),
+readlink().
 
-Chris Nandor and Matthias Neeracher have integrated the MacPerl changes
-into 5.6.0.
+=head1 Tasks that need a knowledge of the interpreter
 
-=head2 Web "nerve center" for Perl
+These tasks would need C knowledge, and knowledge of how the interpreter works,
+or a willingness to learn.
 
-http://use.perl.org/ is what you're looking for.
+=head2 Implement $value ~~ 0 .. $range
 
-=head2 Regular expression tutorial
+It would be nice to extend the syntax of the C<~~> operator to also
+understand numeric (and maybe alphanumeric) ranges.
 
-C<perlretut>, provided by Mark Kvale.
-
-=head2 Debugging Tutorial
-
-C<perldebtut>, written by Richard Foley.
-
-=head2 Integrate new modules
-
-Jarkko has been integrating madly into 5.7.x
-
-=head2 Integrate profiler
-
-C<Devel::DProf> is now a core module.
-
-=head2 Y2K error detection
-
-There's a configure option to detect unsafe concatenation with "19", and
-a CPAN module. (C<D'oh::Year>)
-
-=head2 Regular expression debugger
-
-While not part of core, Mark-Jason Dominus has written C<Rx> and has
-also come up with a generalised strategy for regular expression
-debugging.
-
-=head2 POD checker
-
-That's, uh, F<podchecker>
-
-=head2 "Dynamic" lexicals
-
-=head2 Cache precompiled modules
-
-=head1 Deprecated Wishes
-
-These are items which used to be in the todo file, but have been
-deprecated for some reason.
-
-=head2 Loop control on do{}
-
-This would break old code; use C<do{{ }}> instead.
-
-=head2 Lexically scoped typeglobs
-
-Not needed now we have lexical IO handles.
-
-=head2 format BOTTOM
-
-=head2 report HANDLE
+=head2 Attach/detach debugger from running program
 
-Damian Conway's text formatting modules seem to be the Way To Go.
+The old perltodo notes "With C<gdb>, you can attach the debugger to a running
+program if you pass the process ID. It would be good to do this with the Perl
+debugger on a running Perl program, although I'm not sure how it would be
+done." ssh and screen do this with named pipes in /tmp. Maybe we can too.
 
-=head2 Generalised want()/caller())
+=head2 LVALUE functions for lists
 
-Robin Houston's C<Want> module does this.
+The old perltodo notes that lvalue functions don't work for list or hash
+slices. This would be good to fix.
 
-=head2 Named prototypes
+=head2 LVALUE functions in the debugger
 
-This seems to be delayed until Perl 6.
+The old perltodo notes that lvalue functions don't work in the debugger. This
+would be good to fix.
 
-=head2 Built-in globbing
+=head2 regexp optimiser optional
 
-The C<File::Glob> module has been used to replace the C<glob> function.
+The regexp optimiser is not optional. It should configurable to be, to allow
+its performance to be measured, and its bugs to be easily demonstrated.
 
-=head2 Regression tests for suidperl
+=head2 delete &function
 
-C<suidperl> is deprecated in favour of common sense.
+Allow to delete functions. One can already undef them, but they're still
+in the stash.
 
-=head2 Cached hash values
+=head2 optional optimizer
 
-We have shared hash keys, which perform the same job.
+Make the peephole optimizer optional. Currently it performs two tasks as
+it walks the optree - genuine peephole optimisations, and necessary fixups of
+ops. It would be good to find an efficient way to switch out the
+optimisations whilst keeping the fixups.
 
-=head2 Add compression modules
+=head2 You WANT *how* many
 
-The compression modules are a little heavy; meanwhile, Nick Clark is
-working on experimental pragmata to do transparent decompression on
-input.
+Currently contexts are void, scalar and list. split has a special mechanism in
+place to pass in the number of return values wanted. It would be useful to
+have a general mechanism for this, backwards compatible and little speed hit.
+This would allow proposals such as short circuiting sort to be implemented
+as a module on CPAN.
 
-=head2 Reorganise documentation into tutorials/references
+=head2 lexical aliases
 
-Could not get consensus on P5P about this.
+Allow lexical aliases (maybe via the syntax C<my \$alias = \$foo>.
 
-=head2 Remove distinction between functions and operators
+=head2 entersub XS vs Perl
 
-Caution: highly flammable.
+At the moment pp_entersub is huge, and has code to deal with entering both
+perl and XS subroutines. Subroutine implementations rarely change between 
+perl and XS at run time, so investigate using 2 ops to enter subs (one for
+XS, one for perl) and swap between if a sub is redefined.
 
-=head2 Make XS easier to use
+=head2 Self ties
 
-Use C<Inline> instead, or SWIG.
+self ties are currently illegal because they caused too many segfaults. Maybe
+the causes of these could be tracked down and self-ties on all types re-
+instated.
 
-=head2 Make embedding easier to use
+=head2 Optimize away @_
 
-Use C<Inline::CPR>.
+The old perltodo notes "Look at the "reification" code in C<av.c>".
 
-=head2 man for perl
+=head2 What hooks would assertions need?
 
-See the Perl Power Tools. ( http://language.perl.com/ppt/ )
+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 my $Package::variable
+=head2 Properly Unicode safe tokeniser and pads.
 
-Use C<our> instead.
+The tokeniser isn't actually very UTF-8 clean. C<use utf8;> is a hack -
+variable names are stored in stashes as raw bytes, without the utf-8 flag
+set. The pad API only takes a C<char *> pointer, so that's all bytes too. The
+tokeniser ignores the UTF-8-ness of C<PL_rsfp>, or any SVs returned from
+source filters.  All this could be fixed.
 
-=head2 "or" tests defined, not truth
+=head1 Big projects
 
-Suggesting this on P5P B<will> cause a boring and interminable flamewar.
+Tasks that will get your name mentioned in the description of the "Highlights
+of 5.10"
 
-=head2 "class"-based lexicals
+=head2 make ithreads more robust
 
-Use flyweight objects, secure hashes or, dare I say it, pseudo-hashes instead.
-(Or whatever will replace pseudohashes in 5.10.)
+Generally make ithreads more robust. See also L</iCOW>
 
-=head2 byteperl
+This task is incremental - even a little bit of work on it will help, and
+will be greatly appreciated.
 
-C<ByteLoader> covers this.
+One bit would be to write the missing code in sv.c:Perl_dirp_dup.
 
-=head2 Lazy evaluation / tail recursion removal
+=head2 iCOW
 
-C<List::Util> gives first() (a short-circuiting grep); tail recursion
-removal is done manually, with C<goto &whoami;>. (However, MJD has
-found that C<goto &whoami> introduces a performance penalty, so maybe
-there should be a way to do this after all: C<sub foo {START: ... goto
-START;> is better.)
+Sarathy and Arthur have a proposal for an improved Copy On Write which
+specifically will be able to COW new ithreads. If this can be implemented
+it would be a good thing.
 
-=head2 Make "use utf8" the default
+=head2 (?{...}) closures in regexps
 
-Because of backward compatibility this is difficult: scripts could not
-contain B<any legacy eight-bit data> (like Latin-1) anymore, even in
-string literals or pod.  Also would introduce a measurable slowdown of
-at least few percentages since all regular expression operations would
-be done in full UTF-8.  But if you want to try this, add
--DUSE_UTF8_SCRIPTS to your compilation flags.
+Fix (or rewrite) the implementation of the C</(?{...})/> closures.
 
-=head2 Unicode collation and normalization
+=head2 A re-entrant regexp engine
 
-The Unicode::Collate and Unicode::Normalize modules
-by SADAHIRO Tomoyuki have been included since 5.8.0.
+This will allow the use of a regex from inside (?{ }), (??{ }) and
+(?(?{ })|) constructs.
 
-    Collation?     http://www.unicode.org/unicode/reports/tr10/
-    Normalization? http://www.unicode.org/unicode/reports/tr15/
+=head2 Add class set operations to regexp engine
 
-=head2 pack/unpack tutorial
+Apparently these are quite useful. Anyway, Jeffery Friedl wants them.
 
-Wolfgang Laun finished what Simon Cozens started.
+demerphq has this on his todo list, but right at the bottom.  
 
-=cut
+