This is a live mirror of the Perl 5 development currently hosted at https://github.com/perl/perl5
The TODO 'Tidy up global variables' can go, replaced with a second
[perl5.git] / pod / perltodo.pod
CommitLineData
7711098a
GS
1=head1 NAME
2
3perltodo - Perl TO-DO List
4
5=head1 DESCRIPTION
e50bb9a1 6
0bdfc961
NC
7This is a list of wishes for Perl. The tasks we think are smaller or easier
8are listed first. Anyone is welcome to work on any of these, but it's a good
9idea to first contact I<perl5-porters@perl.org> to avoid duplication of
10effort. By all means contact a pumpking privately first if you prefer.
e50bb9a1 11
0bdfc961
NC
12Whilst patches to make the list shorter are most welcome, ideas to add to
13the list are also encouraged. Check the perl5-porters archives for past
14ideas, and any discussion about them. One set of archives may be found at:
e50bb9a1 15
0bdfc961 16 http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/
938c8732 17
617eabfa
NC
18What can we offer you in return? Fame, fortune, and everlasting glory? Maybe
19not, but if your patch is incorporated, then we'll add your name to the
20F<AUTHORS> file, which ships in the official distribution. How many other
21programming languages offer you 1 line of immortality?
938c8732 22
4e577f8b 23=head1 The roadmap to 5.10
938c8732 24
4e577f8b
NC
25The roadmap to 5.10 envisages feature based releases, as various items in this
26TODO are completed.
27
4e577f8b
NC
28=head2 Needed for a 5.9.4 release
29
30=over
31
32=item *
78ef48ad
RGS
33
34Review assertions. Review syntax to combine assertions. Assertions could take
35advantage of the lexical pragmas work. L</What hooks would assertions need?>
4e577f8b
NC
36
37=back
38
39=head2 Needed for a 5.9.5 release
40
41=over
42
43=item *
44Implement L</_ prototype character>
45
46=item *
47Implement L</state variables>
48
49=back
50
51=head2 Needed for a 5.9.6 release
52
53Stabilisation. If all goes well, this will be the equivalent of a 5.10-beta.
e50bb9a1 54
0bdfc961 55=head1 Tasks that only need Perl knowledge
e50bb9a1 56
0bdfc961 57=head2 common test code for timed bail out
e50bb9a1 58
0bdfc961
NC
59Write portable self destruct code for tests to stop them burning CPU in
60infinite loops. This needs to avoid using alarm, as some of the tests are
61testing alarm/sleep or timers.
e50bb9a1 62
0bdfc961 63=head2 POD -> HTML conversion in the core still sucks
e50bb9a1 64
938c8732 65Which is crazy given just how simple POD purports to be, and how simple HTML
adebf063
NC
66can be. It's not actually I<as> simple as it sounds, particularly with the
67flexibility POD allows for C<=item>, but it would be good to improve the
68visual appeal of the HTML generated, and to avoid it having any validation
69errors. See also L</make HTML install work>, as the layout of installation tree
70is needed to improve the cross-linking.
938c8732 71
dc0fb092
SP
72The addition of C<Pod::Simple> and its related modules may make this task
73easier to complete.
74
aa237293
NC
75=head2 Parallel testing
76
77The core regression test suite is getting ever more comprehensive, which has
78the side effect that it takes longer to run. This isn't so good. Investigate
79whether it would be feasible to give the harness script the B<option> of
80running sets of tests in parallel. This would be useful for tests in
81F<t/op/*.t> and F<t/uni/*.t> and maybe some sets of tests in F<lib/>.
82
83Questions to answer
84
85=over 4
86
87=item 1
88
89How does screen layout work when you're running more than one test?
90
91=item 2
92
93How does the caller of test specify how many tests to run in parallel?
94
95=item 3
96
97How do setup/teardown tests identify themselves?
98
99=back
100
101Pugs already does parallel testing - can their approach be re-used?
102
0bdfc961 103=head2 Make Schwern poorer
e50bb9a1 104
0bdfc961
NC
105We should have for everything. When all the core's modules are tested,
106Schwern has promised to donate to $500 to TPF. We may need volunteers to
107hold him upside down and shake vigorously in order to actually extract the
108cash.
3958b146 109
0bdfc961 110See F<t/lib/1_compile.t> for the 3 remaining modules that need tests.
e50bb9a1 111
0bdfc961 112=head2 Improve the coverage of the core tests
e50bb9a1 113
0bdfc961
NC
114Use Devel::Cover to ascertain the core's test coverage, then add tests that
115are currently missing.
30222c0f 116
0bdfc961 117=head2 test B
e50bb9a1 118
0bdfc961 119A full test suite for the B module would be nice.
e50bb9a1 120
0bdfc961 121=head2 A decent benchmark
e50bb9a1 122
617eabfa 123C<perlbench> seems impervious to any recent changes made to the perl core. It
0bdfc961
NC
124would be useful to have a reasonable general benchmarking suite that roughly
125represented what current perl programs do, and measurably reported whether
126tweaks to the core improve, degrade or don't really affect performance, to
127guide people attempting to optimise the guts of perl. Gisle would welcome
128new tests for perlbench.
6168cf99 129
0bdfc961 130=head2 fix tainting bugs
6168cf99 131
0bdfc961
NC
132Fix the bugs revealed by running the test suite with the C<-t> switch (via
133C<make test.taintwarn>).
e50bb9a1 134
0bdfc961 135=head2 Dual life everything
e50bb9a1 136
0bdfc961
NC
137As part of the "dists" plan, anything that doesn't belong in the smallest perl
138distribution needs to be dual lifed. Anything else can be too. Figure out what
139changes would be needed to package that module and its tests up for CPAN, and
140do so. Test it with older perl releases, and fix the problems you find.
e50bb9a1 141
0bdfc961 142=head2 Improving C<threads::shared>
722d2a37 143
0bdfc961
NC
144Investigate whether C<threads::shared> could share aggregates properly with
145only Perl level changes to shared.pm
722d2a37 146
0bdfc961 147=head2 POSIX memory footprint
e50bb9a1 148
0bdfc961
NC
149Ilya observed that use POSIX; eats memory like there's no tomorrow, and at
150various times worked to cut it down. There is probably still fat to cut out -
151for example POSIX passes Exporter some very memory hungry data structures.
e50bb9a1 152
e50bb9a1 153
e50bb9a1 154
e50bb9a1 155
e50bb9a1 156
adebf063 157
adebf063 158
0bdfc961 159=head1 Tasks that need a little sysadmin-type knowledge
e50bb9a1 160
0bdfc961
NC
161Or if you prefer, tasks that you would learn from, and broaden your skills
162base...
e50bb9a1 163
617eabfa
NC
164=head2 Relocatable perl
165
166The C level patches needed to create a relocatable perl binary are done, as
167is the work on F<Config.pm>. All that's left to do is the C<Configure> tweaking
168to let people specify how they want to do the install.
169
cd793d32 170=head2 make HTML install work
e50bb9a1 171
adebf063
NC
172There is an C<installhtml> target in the Makefile. It's marked as
173"experimental". It would be good to get this tested, make it work reliably, and
174remove the "experimental" tag. This would include
175
176=over 4
177
178=item 1
179
180Checking that cross linking between various parts of the documentation works.
181In particular that links work between the modules (files with POD in F<lib/>)
182and the core documentation (files in F<pod/>)
183
184=item 2
185
617eabfa
NC
186Work out how to split C<perlfunc> into chunks, preferably one per function
187group, preferably with general case code that could be used elsewhere.
188Challenges here are correctly identifying the groups of functions that go
189together, and making the right named external cross-links point to the right
190page. Things to be aware of are C<-X>, groups such as C<getpwnam> to
191C<endservent>, two or more C<=items> giving the different parameter lists, such
192as
adebf063
NC
193
194 =item substr EXPR,OFFSET,LENGTH,REPLACEMENT
195
196 =item substr EXPR,OFFSET,LENGTH
197
198 =item substr EXPR,OFFSET
199
200and different parameter lists having different meanings. (eg C<select>)
201
202=back
3a89a73c 203
0bdfc961
NC
204=head2 compressed man pages
205
206Be able to install them. This would probably need a configure test to see how
207the system does compressed man pages (same directory/different directory?
208same filename/different filename), as well as tweaking the F<installman> script
209to compress as necessary.
210
30222c0f
NC
211=head2 Add a code coverage target to the Makefile
212
213Make it easy for anyone to run Devel::Cover on the core's tests. The steps
214to do this manually are roughly
215
216=over 4
217
218=item *
219
220do a normal C<Configure>, but include Devel::Cover as a module to install
221(see F<INSTALL> for how to do this)
222
223=item *
224
225 make perl
226
227=item *
228
229 cd t; HARNESS_PERL_SWITCHES=-MDevel::Cover ./perl -I../lib harness
230
231=item *
232
233Process the resulting Devel::Cover database
234
235=back
236
237This just give you the coverage of the F<.pm>s. To also get the C level
238coverage you need to
239
240=over 4
241
242=item *
243
244Additionally tell C<Configure> to use the appropriate C compiler flags for
245C<gcov>
246
247=item *
248
249 make perl.gcov
250
251(instead of C<make perl>)
252
253=item *
254
255After running the tests run C<gcov> to generate all the F<.gcov> files.
256(Including down in the subdirectories of F<ext/>
257
258=item *
259
260(From the top level perl directory) run C<gcov2perl> on all the C<.gcov> files
261to get their stats into the cover_db directory.
262
263=item *
264
265Then process the Devel::Cover database
266
267=back
268
269It would be good to add a single switch to C<Configure> to specify that you
270wanted to perform perl level coverage, and another to specify C level
271coverage, and have C<Configure> and the F<Makefile> do all the right things
272automatically.
273
0bdfc961
NC
274=head2 Make Config.pm cope with differences between build and installed perl
275
276Quite often vendors ship a perl binary compiled with their (pay-for)
277compilers. People install a free compiler, such as gcc. To work out how to
278build extensions, Perl interrogates C<%Config>, so in this situation
279C<%Config> describes compilers that aren't there, and extension building
280fails. This forces people into choosing between re-compiling perl themselves
281using the compiler they have, or only using modules that the vendor ships.
282
283It would be good to find a way teach C<Config.pm> about the installation setup,
284possibly involving probing at install time or later, so that the C<%Config> in
285a binary distribution better describes the installed machine, when the
286installed machine differs from the build machine in some significant way.
287
46925299 288=head2 make parallel builds work
0bdfc961 289
46925299
NC
290Currently parallel builds (such as C<make -j3>) don't work reliably. We believe
291that this is due to incomplete dependency specification in the F<Makefile>.
292It would be good if someone were able to track down the causes of these
293problems, so that parallel builds worked properly.
0bdfc961 294
728f4ecd
NC
295=head2 linker specification files
296
297Some platforms mandate that you provide a list of a shared library's external
298symbols to the linker, so the core already has the infrastructure in place to
299do this for generating shared perl libraries. My understanding is that the
300GNU toolchain can accept an optional linker specification file, and restrict
301visibility just to symbols declared in that file. It would be good to extend
302F<makedef.pl> to support this format, and to provide a means within
303C<Configure> to enable it. This would allow Unix users to test that the
304export list is correct, and to build a perl that does not pollute the global
305namespace with private symbols.
306
8523e164 307
0bdfc961
NC
308
309
310=head1 Tasks that need a little C knowledge
311
312These tasks would need a little C knowledge, but don't need any specific
313background or experience with XS, or how the Perl interpreter works
314
315=head2 Make it clear from -v if this is the exact official release
89007cb3 316
617eabfa
NC
317Currently perl from C<p4>/C<rsync> ships with a F<patchlevel.h> file that
318usually defines one local patch, of the form "MAINT12345" or "RC1". The output
319of perl -v doesn't report that a perl isn't an official release, and this
89007cb3 320information can get lost in bugs reports. Because of this, the minor version
fa11829f 321isn't bumped up until RC time, to minimise the possibility of versions of perl
89007cb3
NC
322escaping that believe themselves to be newer than they actually are.
323
324It would be useful to find an elegant way to have the "this is an interim
325maintenance release" or "this is a release candidate" in the terse -v output,
326and have it so that it's easy for the pumpking to remove this just as the
327release tarball is rolled up. This way the version pulled out of rsync would
328always say "I'm a development release" and it would be safe to bump the
329reported minor version as soon as a release ships, which would aid perl
330developers.
331
0bdfc961
NC
332This task is really about thinking of an elegant way to arrange the C source
333such that it's trivial for the Pumpking to flag "this is an official release"
334when making a tarball, yet leave the default source saying "I'm not the
335official release".
336
0f788cd2
NC
337=head2 Ordering of "global" variables.
338
339F<thrdvar.h> and F<intrpvarh> define the "global" variables that need to be
340per-thread under ithreads, where the variables are actually elements in a
341structure. As C dictates, the variables must be laid out in order of
342declaration. There is a comment
343C</* Important ones in the first cache line (if alignment is done right) */>
344which implies that at some point in the past the ordering was carefully chosen
345(at least in part). However, it's clear that the ordering is less than perfect,
346as currently there are things such as 7 C<bool>s in a row, then something
347typically requiring 4 byte alignment, and then an odd C<bool> later on.
348(C<bool>s are typically defined as C<char>s). So it would be good for someone
349to review the ordering of the variables, to see how much alignment padding can
350be removed.
351
d7939546
NC
352It's also worth checking that all variables are actually used. Perl 5.8.0
353shipped with C<PL_nrs> still defined in F<thrdvar.h>, despite it being unused
354since a change over a year earlier. Had this been spotted before release, it
355could have been removed, but now it has to remain in the 5.8.x releases to
356keep the structure the same size, to retain binary compatibility.
357
62403a3c
NC
358=head2 am I hot or not?
359
360The idea of F<pp_hot.c> is that it contains the I<hot> ops, the ops that are
361most commonly used. The idea is that by grouping them, their object code will
362be adjacent in the executable, so they have a greater chance of already being
363in the CPU cache (or swapped in) due to being near another op already in use.
364
365Except that it's not clear if these really are the most commonly used ops. So
366anyone feeling like exercising their skill with coverage and profiling tools
367might want to determine what ops I<really> are the most commonly used. And in
368turn suggest evictions and promotions to achieve a better F<pp_hot.c>.
369
c99e3826
NC
370=head2 emulate the per-thread memory pool on Unix
371
372For Windows, ithreads allocates memory for each thread from a separate pool,
373which it discards at thread exit. It also checks that memory is free()d to
374the correct pool. Neither check is done on Unix, so code developed there won't
375be subject to such strictures, so can harbour bugs that only show up when the
376code reaches Windows.
377
378It would be good to be able to optionally emulate the Window pool system on
379Unix, to let developers who only have access to Unix, or want to use
380Unix-specific debugging tools, check for these problems. To do this would
381involve figuring out how the C<PerlMem_*> macros wrap C<malloc()> access, and
382providing a layer that records/checks the identity of the thread making the
383call, and recording all the memory allocated by each thread via this API so
384that it can be summarily free()d at thread exit. One implementation idea
385would be to increase the size of allocation, and store the C<my_perl> pointer
386(to identify the thread) at the start, along with pointers to make a linked
387list of blocks for this thread. To avoid alignment problems it would be
388necessary to do something like
389
390 union memory_header_padded {
391 struct memory_header {
392 void *thread_id; /* For my_perl */
393 void *next; /* Pointer to next block for this thread */
394 } data;
395 long double padding; /* whatever type has maximal alignment constraint */
396 };
397
398
399although C<long double> might not be the only type to add to the padding
400union.
62403a3c 401
077e3186
NC
402=head2 reduce duplication in sv_setsv_flags
403
404C<Perl_sv_setsv_flags> has a comment
405C</* There's a lot of redundancy below but we're going for speed here */>
406
407Whilst this was true 10 years ago, the growing disparity between RAM and CPU
408speeds mean that the trade offs have changed. In addition, the duplicate code
409adds to the maintenance burden. It would be good to see how much of the
410redundancy can be pruned, particular in the less common paths. (Profiling
411tools at the ready...). For example, why does the test for
412"Can't redefine active sort subroutine" need to occur in two places?
413
0bdfc961
NC
414
415
416
0bdfc961 417=head1 Tasks that need a knowledge of XS
e50bb9a1 418
0bdfc961
NC
419These tasks would need C knowledge, and roughly the level of knowledge of
420the perl API that comes from writing modules that use XS to interface to
421C.
422
423=head2 IPv6
424
425Clean this up. Check everything in core works
426
4a750395
NC
427=head2 shrink C<GV>s, C<CV>s
428
429By removing unused elements and careful re-ordering, the structures for C<AV>s
430and C<HV>s have recently been shrunk considerably. It's probable that the same
431approach would find savings in C<GV>s and C<CV>s, if not all the other
432larger-than-C<PVMG> types.
433
e593da1a
NC
434=head2 merge Perl_sv_2[inpu]v
435
436There's a lot of code shared between C<Perl_sv_2iv_flags>,
437C<Perl_sv_2uv_flags>, C<Perl_sv_2nv>, and C<Perl_sv_2pv_flags>. It would be
438interesting to see if some of it can be merged into common shared static
439functions. In particular, C<Perl_sv_2uv_flags> started out as a cut&paste
440from C<Perl_sv_2iv_flags> around 5.005_50 time, and it may be possible to
441replace both with a single function that returns a value or union which is
442split out by the macros in F<sv.h>
443
0bdfc961
NC
444=head2 UTF8 caching code
445
446The string position/offset cache is not optional. It should be.
447
448=head2 Implicit Latin 1 => Unicode translation
449
450Conversions from byte strings to UTF-8 currently map high bit characters
451to Unicode without translation (or, depending on how you look at it, by
452implicitly assuming that the byte strings are in Latin-1). As perl assumes
453the C locale by default, upgrading a string to UTF-8 may change the
454meaning of its contents regarding character classes, case mapping, etc.
455This should probably emit a warning (at least).
456
457This task is incremental - even a little bit of work on it will help.
e50bb9a1 458
cd793d32 459=head2 autovivification
e50bb9a1 460
cd793d32 461Make all autovivification consistent w.r.t LVALUE/RVALUE and strict/no strict;
e50bb9a1 462
0bdfc961 463This task is incremental - even a little bit of work on it will help.
e50bb9a1 464
0bdfc961 465=head2 Unicode in Filenames
e50bb9a1 466
0bdfc961
NC
467chdir, chmod, chown, chroot, exec, glob, link, lstat, mkdir, open,
468opendir, qx, readdir, readlink, rename, rmdir, stat, symlink, sysopen,
469system, truncate, unlink, utime, -X. All these could potentially accept
470Unicode filenames either as input or output (and in the case of system
471and qx Unicode in general, as input or output to/from the shell).
472Whether a filesystem - an operating system pair understands Unicode in
473filenames varies.
e50bb9a1 474
0bdfc961
NC
475Known combinations that have some level of understanding include
476Microsoft NTFS, Apple HFS+ (In Mac OS 9 and X) and Apple UFS (in Mac
477OS X), NFS v4 is rumored to be Unicode, and of course Plan 9. How to
478create Unicode filenames, what forms of Unicode are accepted and used
479(UCS-2, UTF-16, UTF-8), what (if any) is the normalization form used,
480and so on, varies. Finding the right level of interfacing to Perl
481requires some thought. Remember that an OS does not implicate a
482filesystem.
e50bb9a1 483
0bdfc961
NC
484(The Windows -C command flag "wide API support" has been at least
485temporarily retired in 5.8.1, and the -C has been repurposed, see
486L<perlrun>.)
969e704b 487
0bdfc961 488=head2 Unicode in %ENV
969e704b 489
0bdfc961 490Currently the %ENV entries are always byte strings.
e50bb9a1 491
0bdfc961 492=head2 use less 'memory'
e50bb9a1 493
0bdfc961
NC
494Investigate trade offs to switch out perl's choices on memory usage.
495Particularly perl should be able to give memory back.
e50bb9a1 496
0bdfc961 497This task is incremental - even a little bit of work on it will help.
0abe3f7c 498
0bdfc961 499=head2 Re-implement C<:unique> in a way that is actually thread-safe
0abe3f7c 500
0bdfc961
NC
501The old implementation made bad assumptions on several levels. A good 90%
502solution might be just to make C<:unique> work to share the string buffer
503of SvPVs. That way large constant strings can be shared between ithreads,
504such as the configuration information in F<Config>.
0abe3f7c 505
0bdfc961 506=head2 Make tainting consistent
0abe3f7c 507
0bdfc961
NC
508Tainting would be easier to use if it didn't take documented shortcuts and
509allow taint to "leak" everywhere within an expression.
0abe3f7c 510
0bdfc961 511=head2 readpipe(LIST)
0abe3f7c 512
0bdfc961
NC
513system() accepts a LIST syntax (and a PROGRAM LIST syntax) to avoid
514running a shell. readpipe() (the function behind qx//) could be similarly
515extended.
0abe3f7c 516
e50bb9a1 517
e50bb9a1 518
e50bb9a1 519
f86a8bc5 520
0bdfc961 521=head1 Tasks that need a knowledge of the interpreter
3298bd4d 522
0bdfc961
NC
523These tasks would need C knowledge, and knowledge of how the interpreter works,
524or a willingness to learn.
3298bd4d 525
0bdfc961
NC
526=head2 lexical pragmas
527
78ef48ad
RGS
528Document the new support for lexical pragmas in 5.9.3 and how %^H works.
529Maybe C<re>, C<encoding>, maybe other pragmas could be made lexical.
0562c0e3 530
d10fc472 531=head2 Attach/detach debugger from running program
1626a787 532
cd793d32
NC
533The old perltodo notes "With C<gdb>, you can attach the debugger to a running
534program if you pass the process ID. It would be good to do this with the Perl
0bdfc961
NC
535debugger on a running Perl program, although I'm not sure how it would be
536done." ssh and screen do this with named pipes in /tmp. Maybe we can too.
1626a787 537
0bdfc961 538=head2 Constant folding
80b46460 539
0bdfc961
NC
540The peephole optimiser should trap errors during constant folding, and give
541up on the folding, rather than bailing out at compile time. It is quite
542possible that the unfoldable constant is in unreachable code, eg something
543akin to C<$a = 0/0 if 0;>
544
545=head2 LVALUE functions for lists
546
547The old perltodo notes that lvalue functions don't work for list or hash
548slices. This would be good to fix.
549
550=head2 LVALUE functions in the debugger
551
552The old perltodo notes that lvalue functions don't work in the debugger. This
553would be good to fix.
554
555=head2 _ prototype character
556
557Study the possibility of adding a new prototype character, C<_>, meaning
558"this argument defaults to $_".
559
4e577f8b
NC
560=head2 state variables
561
562C<my $foo if 0;> is deprecated, and should be replaced with
563C<state $x = "initial value\n";> the syntax from Perl 6.
564
0bdfc961
NC
565=head2 @INC source filter to Filter::Simple
566
567The second return value from a sub in @INC can be a source filter. This isn't
568documented. It should be changed to use Filter::Simple, tested and documented.
569
570=head2 regexp optimiser optional
571
572The regexp optimiser is not optional. It should configurable to be, to allow
573its performance to be measured, and its bugs to be easily demonstrated.
574
575=head2 UNITCHECK
576
577Introduce a new special block, UNITCHECK, which is run at the end of a
578compilation unit (module, file, eval(STRING) block). This will correspond to
579the Perl 6 CHECK. Perl 5's CHECK cannot be changed or removed because the
580O.pm/B.pm backend framework depends on it.
581
582=head2 optional optimizer
583
584Make the peephole optimizer optional. Currently it performs two tasks as
585it walks the optree - genuine peephole optimisations, and necessary fixups of
586ops. It would be good to find an efficient way to switch out the
587optimisations whilst keeping the fixups.
588
589=head2 You WANT *how* many
590
591Currently contexts are void, scalar and list. split has a special mechanism in
592place to pass in the number of return values wanted. It would be useful to
593have a general mechanism for this, backwards compatible and little speed hit.
594This would allow proposals such as short circuiting sort to be implemented
595as a module on CPAN.
596
597=head2 lexical aliases
598
599Allow lexical aliases (maybe via the syntax C<my \$alias = \$foo>.
600
601=head2 entersub XS vs Perl
602
603At the moment pp_entersub is huge, and has code to deal with entering both
604perl and XS subroutines. Subroutine implementations rarely change between
605perl and XS at run time, so investigate using 2 ops to enter subs (one for
606XS, one for perl) and swap between if a sub is redefined.
2810d901
NC
607
608=head2 Self ties
609
610self ties are currently illegal because they caused too many segfaults. Maybe
611the causes of these could be tracked down and self-ties on all types re-
612instated.
0bdfc961
NC
613
614=head2 Optimize away @_
615
616The old perltodo notes "Look at the "reification" code in C<av.c>".
617
0bdfc961
NC
618=head2 What hooks would assertions need?
619
620Assertions are in the core, and work. However, assertions needed to be added
621as a core patch, rather than an XS module in ext, or a CPAN module, because
622the core has no hooks in the necessary places. It would be useful to
623investigate what hooks would need to be added to make it possible to provide
624the full assertion support from a CPAN module, so that we aren't constraining
625the imagination of future CPAN authors.
626
627
628
629
630
0bdfc961
NC
631=head1 Big projects
632
633Tasks that will get your name mentioned in the description of the "Highlights
634of 5.10"
635
636=head2 make ithreads more robust
637
4e577f8b 638Generally make ithreads more robust. See also L</iCOW>
0bdfc961
NC
639
640This task is incremental - even a little bit of work on it will help, and
641will be greatly appreciated.
642
6c047da7
YST
643One bit would be to write the missing code in sv.c:Perl_dirp_dup.
644
0bdfc961
NC
645=head2 iCOW
646
647Sarathy and Arthur have a proposal for an improved Copy On Write which
648specifically will be able to COW new ithreads. If this can be implemented
649it would be a good thing.
650
651=head2 (?{...}) closures in regexps
652
653Fix (or rewrite) the implementation of the C</(?{...})/> closures.
654
655=head2 A re-entrant regexp engine
656
657This will allow the use of a regex from inside (?{ }), (??{ }) and
658(?(?{ })|) constructs.