.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.32
.\" ========================================================================
.de Sh \" Subsection heading
.de Sp \" Vertical space (when we can't use .PP)
.de Vb \" Begin verbatim text
.de Ve \" End verbatim text
.\" Set up some character translations and predefined strings. \*(-- will
.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
.\" double quote, and \*(R" will give a right double quote. | will give a
.\" real vertical bar. \*(C+ will give a nicer C++. Capital omega is used to
.\" do unbreakable dashes and therefore won't be available. \*(C` and \*(C'
.\" expand to `' in nroff, nothing in troff, for use with C<>.
.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
. if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
. if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch
.\" If the F register is turned on, we'll generate index entries on stderr for
.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
. tm Index:\\$1\t\\n%\t"\\$2"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear. Run. Save yourself. No user-serviceable parts.
. \" fudge factors for nroff and troff
. ds #H ((1u-(\\\\n(.fu%2u))*.13m)
. \" simple accents for nroff and troff
. ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
. ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
. ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
. ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
. ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
. ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
. \" troff and (daisy-wheel) nroff accents
.ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
.ds 8 \h'\*(#H'\(*b\h'-\*(#H'
.ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
.ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
.ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
.ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
.ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
.ds ae a\h'-(\w'a'u*4/10)'e
.ds Ae A\h'-(\w'A'u*4/10)'E
. \" corrections for vroff
.if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
.if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
. \" for low resolution devices (crt and lpr)
.if \n(.H>23 .if \n(.V>19 \
.\" ========================================================================
.TH PERLTODO 1 "2006-01-07" "perl v5.8.8" "Perl Programmers Reference Guide"
perltodo \- Perl TO\-DO List
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 \fIperl5\-porters@perl.org\fR 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/
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
\&\fI\s-1AUTHORS\s0\fR file, which ships in the official distribution. How many other
programming languages offer you 1 line of immortality?
.SH "The roadmap to 5.10"
.IX Header "The roadmap to 5.10"
The roadmap to 5.10 envisages feature based releases, as various items in this
\&\s-1TODO\s0 are completed.
.Sh "Needed for a 5.9.4 release"
.IX Subsection "Needed for a 5.9.4 release"
Review assertions. Review syntax to combine assertions. Assertions could take
advantage of the lexical pragmas work. \*(L"What hooks would assertions need?\*(R"
.Sh "Needed for a 5.9.5 release"
.IX Subsection "Needed for a 5.9.5 release"
.ie n .IP "* Implement ""_ prototype character""" 4
.el .IP "* Implement ``_ prototype character''" 4
.IX Item "Implement _ prototype character"
.ie n .IP "* Implement ""state variables""" 4
.el .IP "* Implement ``state variables''" 4
.IX Item "Implement state variables"
.Sh "Needed for a 5.9.6 release"
.IX Subsection "Needed for a 5.9.6 release"
Stabilisation. If all goes well, this will be the equivalent of a 5.10\-beta.
.SH "Tasks that only need Perl knowledge"
.IX Header "Tasks that only need Perl knowledge"
.Sh "common test code for timed bail out"
.IX Subsection "common test code for timed bail out"
Write portable self destruct code for tests to stop them burning \s-1CPU\s0 in
infinite loops. This needs to avoid using alarm, as some of the tests are
testing alarm/sleep or timers.
.Sh "\s-1POD\s0 \-> \s-1HTML\s0 conversion in the core still sucks"
.IX Subsection "POD -> HTML conversion in the core still sucks"
Which is crazy given just how simple \s-1POD\s0 purports to be, and how simple \s-1HTML\s0
can be. It's not actually \fIas\fR simple as it sounds, particularly with the
flexibility \s-1POD\s0 allows for \f(CW\*(C`=item\*(C'\fR, but it would be good to improve the
visual appeal of the \s-1HTML\s0 generated, and to avoid it having any validation
errors. See also \*(L"make \s-1HTML\s0 install work\*(R", as the layout of installation tree
is needed to improve the cross\-linking.
The addition of \f(CW\*(C`Pod::Simple\*(C'\fR and its related modules may make this task
.IX Subsection "Parallel testing"
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 \fBoption\fR of
running sets of tests in parallel. This would be useful for tests in
\&\fIt/op/*.t\fR and \fIt/uni/*.t\fR and maybe some sets of tests in \fIlib/\fR.
How does screen layout work when you're running more than one test?
How does the caller of test specify how many tests to run in parallel?
How do setup/teardown tests identify themselves?
Pugs already does parallel testing \- can their approach be re\-used?
.Sh "Make Schwern poorer"
.IX Subsection "Make Schwern poorer"
We should have for everything. When all the core's modules are tested,
Schwern has promised to donate to \f(CW$500\fR to \s-1TPF\s0. We may need volunteers to
hold him upside down and shake vigorously in order to actually extract the
See \fIt/lib/1_compile.t\fR for the 3 remaining modules that need tests.
.Sh "Improve the coverage of the core tests"
.IX Subsection "Improve the coverage of the core tests"
Use Devel::Cover to ascertain the core's test coverage, then add tests that
A full test suite for the B module would be nice.
.IX Subsection "A decent benchmark"
\&\f(CW\*(C`perlbench\*(C'\fR 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
.IX Subsection "fix tainting bugs"
Fix the bugs revealed by running the test suite with the \f(CW\*(C`\-t\*(C'\fR switch (via
\&\f(CW\*(C`make test.taintwarn\*(C'\fR).
.Sh "Dual life everything"
.IX Subsection "Dual life everything"
As part of the \*(L"dists\*(R" 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 \s-1CPAN\s0, and
do so. Test it with older perl releases, and fix the problems you find.
.ie n .Sh "Improving ""threads::shared"""
.el .Sh "Improving \f(CWthreads::shared\fP"
.IX Subsection "Improving threads::shared"
Investigate whether \f(CW\*(C`threads::shared\*(C'\fR could share aggregates properly with
only Perl level changes to shared.pm
.Sh "\s-1POSIX\s0 memory footprint"
.IX Subsection "POSIX memory footprint"
Ilya observed that use \s-1POSIX\s0; 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 \s-1POSIX\s0 passes Exporter some very memory hungry data structures.
.SH "Tasks that need a little sysadmin-type knowledge"
.IX Header "Tasks that need a little sysadmin-type knowledge"
Or if you prefer, tasks that you would learn from, and broaden your skills
.IX Subsection "Relocatable perl"
The C level patches needed to create a relocatable perl binary are done, as
is the work on \fIConfig.pm\fR. All that's left to do is the \f(CW\*(C`Configure\*(C'\fR tweaking
to let people specify how they want to do the install.
.Sh "make \s-1HTML\s0 install work"
.IX Subsection "make HTML install work"
There is an \f(CW\*(C`installhtml\*(C'\fR target in the Makefile. It's marked as
\&\*(L"experimental\*(R". It would be good to get this tested, make it work reliably, and
remove the \*(L"experimental\*(R" tag. This would include
Checking that cross linking between various parts of the documentation works.
In particular that links work between the modules (files with \s-1POD\s0 in \fIlib/\fR)
and the core documentation (files in \fIpod/\fR)
Work out how to split \f(CW\*(C`perlfunc\*(C'\fR 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 \f(CW\*(C`\-X\*(C'\fR, groups such as \f(CW\*(C`getpwnam\*(C'\fR to
\&\f(CW\*(C`endservent\*(C'\fR, two or more \f(CW\*(C`=items\*(C'\fR giving the different parameter lists, such
\& =item substr EXPR,OFFSET,LENGTH,REPLACEMENT
\& =item substr EXPR,OFFSET,LENGTH
\& =item substr EXPR,OFFSET
and different parameter lists having different meanings. (eg \f(CW\*(C`select\*(C'\fR)
.Sh "compressed man pages"
.IX Subsection "compressed man pages"
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 \fIinstallman\fR script
to compress as necessary.
.Sh "Add a code coverage target to the Makefile"
.IX Subsection "Add a code coverage target to the Makefile"
Make it easy for anyone to run Devel::Cover on the core's tests. The steps
to do this manually are roughly
do a normal \f(CW\*(C`Configure\*(C'\fR, but include Devel::Cover as a module to install
(see \fI\s-1INSTALL\s0\fR for how to do this)
\& cd t; HARNESS_PERL_SWITCHES=-MDevel::Cover ./perl -I../lib harness
Process the resulting Devel::Cover database
This just give you the coverage of the \fI.pm\fRs. To also get the C level
Additionally tell \f(CW\*(C`Configure\*(C'\fR to use the appropriate C compiler flags for
(instead of \f(CW\*(C`make perl\*(C'\fR)
After running the tests run \f(CW\*(C`gcov\*(C'\fR to generate all the \fI.gcov\fR files.
(Including down in the subdirectories of \fIext/\fR
(From the top level perl directory) run \f(CW\*(C`gcov2perl\*(C'\fR on all the \f(CW\*(C`.gcov\*(C'\fR files
to get their stats into the cover_db directory.
Then process the Devel::Cover database
It would be good to add a single switch to \f(CW\*(C`Configure\*(C'\fR to specify that you
wanted to perform perl level coverage, and another to specify C level
coverage, and have \f(CW\*(C`Configure\*(C'\fR and the \fIMakefile\fR do all the right things
.Sh "Make Config.pm cope with differences between build and installed perl"
.IX Subsection "Make Config.pm cope with differences between build 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 \f(CW%Config\fR, so in this situation
\&\f(CW%Config\fR 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 \f(CW\*(C`Config.pm\*(C'\fR about the installation setup,
possibly involving probing at install time or later, so that the \f(CW%Config\fR in
a binary distribution better describes the installed machine, when the
installed machine differs from the build machine in some significant way.
.Sh "make parallel builds work"
.IX Subsection "make parallel builds work"
Currently parallel builds (such as \f(CW\*(C`make \-j3\*(C'\fR) don't work reliably. We believe
that this is due to incomplete dependency specification in the \fIMakefile\fR.
It would be good if someone were able to track down the causes of these
problems, so that parallel builds worked properly.
.Sh "linker specification files"
.IX Subsection "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
\&\s-1GNU\s0 toolchain can accept an optional linker specification file, and restrict
visibility just to symbols declared in that file. It would be good to extend
\&\fImakedef.pl\fR to support this format, and to provide a means within
\&\f(CW\*(C`Configure\*(C'\fR 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.
.SH "Tasks that need a little C knowledge"
.IX Header "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 \s-1XS\s0, or how the Perl interpreter works
.Sh "Make it clear from \-v if this is the exact official release"
.IX Subsection "Make it clear from -v if this is the exact official release"
Currently perl from \f(CW\*(C`p4\*(C'\fR/\f(CW\*(C`rsync\*(C'\fR ships with a \fIpatchlevel.h\fR file that
usually defines one local patch, of the form \*(L"\s-1MAINT12345\s0\*(R" or \*(L"\s-1RC1\s0\*(R". 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 \s-1RC\s0 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 \*(L"this is an interim
maintenance release\*(R" or \*(L"this is a release candidate\*(R" 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 \*(L"I'm a development release\*(R" and it would be safe to bump the
reported minor version as soon as a release ships, which would aid perl
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 \*(L"this is an official release\*(R"
when making a tarball, yet leave the default source saying \*(L"I'm not the
.Sh "Tidy up global variables"
.IX Subsection "Tidy up global variables"
There's a note in \fIintrpvar.h\fR
\& /* These two variables are needed to preserve 5.8.x bincompat because
\& we can't change function prototypes of two exported functions.
\& Probably should be taken out of blead soon, and relevant prototypes
So doing this, and removing any of the unused variables still present would
.ie n .Sh "Ordering of ""global"" variables."
.el .Sh "Ordering of ``global'' variables."
.IX Subsection "Ordering of global variables."
\&\fIthrdvar.h\fR and \fIintrpvarh\fR define the \*(L"global\*(R" 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
\&\f(CW\*(C`/* Important ones in the first cache line (if alignment is done right) */\*(C'\fR
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 \f(CW\*(C`bool\*(C'\fRs in a row, then something
typically requiring 4 byte alignment, and then an odd \f(CW\*(C`bool\*(C'\fR later on.
(\f(CW\*(C`bool\*(C'\fRs are typically defined as \f(CW\*(C`char\*(C'\fRs). So it would be good for someone
to review the ordering of the variables, to see how much alignment padding can
.Sh "bincompat functions"
.IX Subsection "bincompat functions"
There are lots of functions which are retained for binary compatibility.
Clean these up. Move them to mathom.c, and don't compile for blead?
.IX Subsection "am I hot or not?"
The idea of \fIpp_hot.c\fR is that it contains the \fIhot\fR 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 \s-1CPU\s0 cache (or swapped in) due to being near another op already in use.
Except that it's not clear if these really are the most commonly used ops. So
anyone feeling like exercising their skill with coverage and profiling tools
might want to determine what ops \fIreally\fR are the most commonly used. And in
turn suggest evictions and promotions to achieve a better \fIpp_hot.c\fR.
.Sh "emulate the per-thread memory pool on Unix"
.IX Subsection "emulate the per-thread memory pool on Unix"
For Windows, ithreads allocates memory for each thread from a separate pool,
which it discards at thread exit. It also checks that memory is \fIfree()\fRd to
the correct pool. Neither check is done on Unix, so code developed there won't
be subject to such strictures, so can harbour bugs that only show up when the
It would be good to be able to optionally emulate the Window pool system on
Unix, to let developers who only have access to Unix, or want to use
Unix-specific debugging tools, check for these problems. To do this would
involve figuring out how the \f(CW\*(C`PerlMem_*\*(C'\fR macros wrap \f(CW\*(C`malloc()\*(C'\fR access, and
providing a layer that records/checks the identity of the thread making the
call, and recording all the memory allocated by each thread via this \s-1API\s0 so
that it can be summarily \fIfree()\fRd at thread exit. One implementation idea
would be to increase the size of allocation, and store the \f(CW\*(C`my_perl\*(C'\fR pointer
(to identify the thread) at the start, along with pointers to make a linked
list of blocks for this thread. To avoid alignment problems it would be
necessary to do something like
\& union memory_header_padded {
\& struct memory_header {
\& void *thread_id; /* For my_perl */
\& void *next; /* Pointer to next block for this thread */
\& long double padding; /* whatever type has maximal alignment constraint */
although \f(CW\*(C`long double\*(C'\fR might not be the only type to add to the padding
.Sh "reduce duplication in sv_setsv_flags"
.IX Subsection "reduce duplication in sv_setsv_flags"
\&\f(CW\*(C`Perl_sv_setsv_flags\*(C'\fR has a comment
\&\f(CW\*(C`/* There's a lot of redundancy below but we're going for speed here */\*(C'\fR
Whilst this was true 10 years ago, the growing disparity between \s-1RAM\s0 and \s-1CPU\s0
speeds mean that the trade offs have changed. In addition, the duplicate code
adds to the maintenance burden. It would be good to see how much of the
redundancy can be pruned, particular in the less common paths. (Profiling
tools at the ready...). For example, why does the test for
\&\*(L"Can't redefine active sort subroutine\*(R" need to occur in two places?
.SH "Tasks that need a knowledge of XS"
.IX Header "Tasks that need a knowledge of XS"
These tasks would need C knowledge, and roughly the level of knowledge of
the perl \s-1API\s0 that comes from writing modules that use \s-1XS\s0 to interface to
Clean this up. Check everything in core works
.ie n .Sh "shrink ""GV""\fPs, \f(CW""CV""s"
.el .Sh "shrink \f(CWGV\fPs, \f(CWCV\fPs"
.IX Subsection "shrink GVs, CVs"
By removing unused elements and careful re\-ordering, the structures for \f(CW\*(C`AV\*(C'\fRs
and \f(CW\*(C`HV\*(C'\fRs have recently been shrunk considerably. It's probable that the same
approach would find savings in \f(CW\*(C`GV\*(C'\fRs and \f(CW\*(C`CV\*(C'\fRs, if not all the other
larger\-than\-\f(CW\*(C`PVMG\*(C'\fR types.
.Sh "merge Perl_sv_2[inpu]v"
.IX Subsection "merge Perl_sv_2[inpu]v"
There's a lot of code shared between \f(CW\*(C`Perl_sv_2iv_flags\*(C'\fR,
\&\f(CW\*(C`Perl_sv_2uv_flags\*(C'\fR, \f(CW\*(C`Perl_sv_2nv\*(C'\fR, and \f(CW\*(C`Perl_sv_2pv_flags\*(C'\fR. It would be
interesting to see if some of it can be merged into common shared static
functions. In particular, \f(CW\*(C`Perl_sv_2uv_flags\*(C'\fR started out as a cut&paste
from \f(CW\*(C`Perl_sv_2iv_flags\*(C'\fR around 5.005_50 time, and it may be possible to
replace both with a single function that returns a value or union which is
split out by the macros in \fIsv.h\fR
.Sh "\s-1UTF8\s0 caching code"
.IX Subsection "UTF8 caching code"
The string position/offset cache is not optional. It should be.
.Sh "Implicit Latin 1 => Unicode translation"
.IX Subsection "Implicit Latin 1 => Unicode translation"
Conversions from byte strings to \s-1UTF\-8\s0 currently map high bit characters
to Unicode without translation (or, depending on how you look at it, by
implicitly assuming that the byte strings are in Latin\-1). As perl assumes
the C locale by default, upgrading a string to \s-1UTF\-8\s0 may change the
meaning of its contents regarding character classes, case mapping, etc.
This should probably emit a warning (at least).
This task is incremental \- even a little bit of work on it will help.
.IX Subsection "autovivification"
Make all autovivification consistent w.r.t \s-1LVALUE/RVALUE\s0 and strict/no strict;
This task is incremental \- even a little bit of work on it will help.
.Sh "Unicode in Filenames"
.IX Subsection "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, \-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
Known combinations that have some level of understanding include
Microsoft \s-1NTFS\s0, Apple \s-1HFS+\s0 (In Mac \s-1OS\s0 9 and X) and Apple \s-1UFS\s0 (in Mac
\&\s-1OS\s0 X), \s-1NFS\s0 v4 is rumored to be Unicode, and of course Plan 9. How to
create Unicode filenames, what forms of Unicode are accepted and used
(\s-1UCS\-2\s0, \s-1UTF\-16\s0, \s-1UTF\-8\s0), what (if any) is the normalization form used,
and so on, varies. Finding the right level of interfacing to Perl
requires some thought. Remember that an \s-1OS\s0 does not implicate a
(The Windows \-C command flag \*(L"wide \s-1API\s0 support\*(R" has been at least
temporarily retired in 5.8.1, and the \-C has been repurposed, see
.ie n .Sh "Unicode in %ENV"
.el .Sh "Unicode in \f(CW%ENV\fP"
.IX Subsection "Unicode in %ENV"
Currently the \f(CW%ENV\fR entries are always byte strings.
.IX Subsection "use less 'memory'"
Investigate trade offs to switch out perl's choices on memory usage.
Particularly perl should be able to give memory back.
This task is incremental \- even a little bit of work on it will help.
.ie n .Sh "Re-implement "":unique"" in a way that is actually thread-safe"
.el .Sh "Re-implement \f(CW:unique\fP in a way that is actually thread-safe"
.IX Subsection "Re-implement :unique in a way that is actually thread-safe"
The old implementation made bad assumptions on several levels. A good 90%
solution might be just to make \f(CW\*(C`:unique\*(C'\fR work to share the string buffer
of SvPVs. That way large constant strings can be shared between ithreads,
such as the configuration information in \fIConfig\fR.
.Sh "Make tainting consistent"
.IX Subsection "Make tainting consistent"
Tainting would be easier to use if it didn't take documented shortcuts and
allow taint to \*(L"leak\*(R" everywhere within an expression.
.Sh "readpipe(\s-1LIST\s0)"
.IX Subsection "readpipe(LIST)"
\&\fIsystem()\fR accepts a \s-1LIST\s0 syntax (and a \s-1PROGRAM\s0 \s-1LIST\s0 syntax) to avoid
running a shell. \fIreadpipe()\fR (the function behind qx//) could be similarly
.SH "Tasks that need a knowledge of the interpreter"
.IX Header "Tasks that need a knowledge of the interpreter"
These tasks would need C knowledge, and knowledge of how the interpreter works,
or a willingness to learn.
.IX Subsection "lexical pragmas"
Document the new support for lexical pragmas in 5.9.3 and how %^H works.
Maybe \f(CW\*(C`re\*(C'\fR, \f(CW\*(C`encoding\*(C'\fR, maybe other pragmas could be made lexical.
.Sh "Attach/detach debugger from running program"
.IX Subsection "Attach/detach debugger from running program"
The old perltodo notes "With \f(CW\*(C`gdb\*(C'\fR, you can attach the debugger to a running
program if you pass the process \s-1ID\s0. 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.
.IX Subsection "Constant folding"
The peephole optimiser should trap errors during constant folding, and give
up on the folding, rather than bailing out at compile time. It is quite
possible that the unfoldable constant is in unreachable code, eg something
akin to \f(CW\*(C`$a = 0/0 if 0;\*(C'\fR
.Sh "\s-1LVALUE\s0 functions for lists"
.IX Subsection "LVALUE functions for lists"
The old perltodo notes that lvalue functions don't work for list or hash
slices. This would be good to fix.
.Sh "\s-1LVALUE\s0 functions in the debugger"
.IX Subsection "LVALUE functions in the debugger"
The old perltodo notes that lvalue functions don't work in the debugger. This
.Sh "_ prototype character"
.IX Subsection "_ prototype character"
Study the possibility of adding a new prototype character, \f(CW\*(C`_\*(C'\fR, meaning
\&\*(L"this argument defaults to \f(CW$_\fR\*(R".
.IX Subsection "state variables"
\&\f(CW\*(C`my $foo if 0;\*(C'\fR is deprecated, and should be replaced with
\&\f(CW\*(C`state $x = "initial value\en";\*(C'\fR the syntax from Perl 6.
.Sh "@INC source filter to Filter::Simple"
.IX Subsection "@INC source filter to Filter::Simple"
The second return value from a sub in \f(CW@INC\fR can be a source filter. This isn't
documented. It should be changed to use Filter::Simple, tested and documented.
.Sh "regexp optimiser optional"
.IX Subsection "regexp optimiser optional"
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.
.IX Subsection "UNITCHECK"
Introduce a new special block, \s-1UNITCHECK\s0, which is run at the end of a
compilation unit (module, file, eval(\s-1STRING\s0) block). This will correspond to
the Perl 6 \s-1CHECK\s0. Perl 5's \s-1CHECK\s0 cannot be changed or removed because the
O.pm/B.pm backend framework depends on it.
.IX Subsection "optional optimizer"
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.
.Sh "You \s-1WANT\s0 *how* many"
.IX Subsection "You WANT *how* many"
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 \s-1CPAN\s0.
.IX Subsection "lexical aliases"
Allow lexical aliases (maybe via the syntax \f(CW\*(C`my \e$alias = \e$foo\*(C'\fR.
.Sh "entersub \s-1XS\s0 vs Perl"
.IX Subsection "entersub XS vs Perl"
At the moment pp_entersub is huge, and has code to deal with entering both
perl and \s-1XS\s0 subroutines. Subroutine implementations rarely change between
perl and \s-1XS\s0 at run time, so investigate using 2 ops to enter subs (one for
\&\s-1XS\s0, one for perl) and swap between if a sub is redefined.
.IX Subsection "Self ties"
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\-
.ie n .Sh "Optimize away @_"
.el .Sh "Optimize away \f(CW@_\fP"
.IX Subsection "Optimize away @_"
The old perltodo notes \*(L"Look at the \*(R"reification" code in \f(CW\*(C`av.c\*(C'\fR".
.Sh "What hooks would assertions need?"
.IX Subsection "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 \s-1XS\s0 module in ext, or a \s-1CPAN\s0 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 \s-1CPAN\s0 module, so that we aren't constraining
the imagination of future \s-1CPAN\s0 authors.
.IX Header "Big projects"
Tasks that will get your name mentioned in the description of the \*(L"Highlights
.Sh "make ithreads more robust"
.IX Subsection "make ithreads more robust"
Generally make ithreads more robust. See also \*(L"iCOW\*(R"
This task is incremental \- even a little bit of work on it will help, and
will be greatly appreciated.
Sarathy and Arthur have a proposal for an improved Copy On Write which
specifically will be able to \s-1COW\s0 new ithreads. If this can be implemented
it would be a good thing.
.Sh "(?{...}) closures in regexps"
.IX Subsection "(?{...}) closures in regexps"
Fix (or rewrite) the implementation of the \f(CW\*(C`/(?{...})/\*(C'\fR closures.
.Sh "A re-entrant regexp engine"
.IX Subsection "A re-entrant regexp engine"
This will allow the use of a regex from inside (?{ }), (??{ }) and
projects / OpenSPARC-T2-SAM / blob