This is a live mirror of the Perl 5 development currently hosted at https://github.com/perl/perl5
A couple of additions in perltodo for the future
[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
0bdfc961 23=head1 Tasks that only need Perl knowledge
e50bb9a1 24
0bdfc961 25=head2 common test code for timed bail out
e50bb9a1 26
0bdfc961
NC
27Write portable self destruct code for tests to stop them burning CPU in
28infinite loops. This needs to avoid using alarm, as some of the tests are
29testing alarm/sleep or timers.
e50bb9a1 30
87a942b1 31=head2 POD -E<gt> HTML conversion in the core still sucks
e50bb9a1 32
938c8732 33Which is crazy given just how simple POD purports to be, and how simple HTML
adebf063
NC
34can be. It's not actually I<as> simple as it sounds, particularly with the
35flexibility POD allows for C<=item>, but it would be good to improve the
36visual appeal of the HTML generated, and to avoid it having any validation
37errors. See also L</make HTML install work>, as the layout of installation tree
38is needed to improve the cross-linking.
938c8732 39
dc0fb092
SP
40The addition of C<Pod::Simple> and its related modules may make this task
41easier to complete.
42
aa237293
NC
43=head2 Parallel testing
44
b2e2905c 45(This probably impacts much more than the core: also the Test::Harness
02f21748
RGS
46and TAP::* modules on CPAN.)
47
aa237293
NC
48The core regression test suite is getting ever more comprehensive, which has
49the side effect that it takes longer to run. This isn't so good. Investigate
50whether it would be feasible to give the harness script the B<option> of
51running sets of tests in parallel. This would be useful for tests in
52F<t/op/*.t> and F<t/uni/*.t> and maybe some sets of tests in F<lib/>.
53
54Questions to answer
55
56=over 4
57
58=item 1
59
60How does screen layout work when you're running more than one test?
61
62=item 2
63
64How does the caller of test specify how many tests to run in parallel?
65
66=item 3
67
68How do setup/teardown tests identify themselves?
69
70=back
71
72Pugs already does parallel testing - can their approach be re-used?
73
0bdfc961 74=head2 Make Schwern poorer
e50bb9a1 75
613bd4f7 76We should have tests for everything. When all the core's modules are tested,
0bdfc961
NC
77Schwern has promised to donate to $500 to TPF. We may need volunteers to
78hold him upside down and shake vigorously in order to actually extract the
79cash.
3958b146 80
0bdfc961 81=head2 Improve the coverage of the core tests
e50bb9a1 82
02f21748
RGS
83Use Devel::Cover to ascertain the core modules's test coverage, then add
84tests that are currently missing.
30222c0f 85
0bdfc961 86=head2 test B
e50bb9a1 87
0bdfc961 88A full test suite for the B module would be nice.
e50bb9a1 89
0bdfc961 90=head2 A decent benchmark
e50bb9a1 91
617eabfa 92C<perlbench> seems impervious to any recent changes made to the perl core. It
0bdfc961
NC
93would be useful to have a reasonable general benchmarking suite that roughly
94represented what current perl programs do, and measurably reported whether
95tweaks to the core improve, degrade or don't really affect performance, to
96guide people attempting to optimise the guts of perl. Gisle would welcome
97new tests for perlbench.
6168cf99 98
0bdfc961 99=head2 fix tainting bugs
6168cf99 100
0bdfc961
NC
101Fix the bugs revealed by running the test suite with the C<-t> switch (via
102C<make test.taintwarn>).
e50bb9a1 103
0bdfc961 104=head2 Dual life everything
e50bb9a1 105
0bdfc961
NC
106As part of the "dists" plan, anything that doesn't belong in the smallest perl
107distribution needs to be dual lifed. Anything else can be too. Figure out what
108changes would be needed to package that module and its tests up for CPAN, and
109do so. Test it with older perl releases, and fix the problems you find.
e50bb9a1 110
a393eb28
RGS
111To make a minimal perl distribution, it's useful to look at
112F<t/lib/commonsense.t>.
113
0bdfc961 114=head2 Improving C<threads::shared>
722d2a37 115
0bdfc961
NC
116Investigate whether C<threads::shared> could share aggregates properly with
117only Perl level changes to shared.pm
722d2a37 118
0bdfc961 119=head2 POSIX memory footprint
e50bb9a1 120
0bdfc961
NC
121Ilya observed that use POSIX; eats memory like there's no tomorrow, and at
122various times worked to cut it down. There is probably still fat to cut out -
123for example POSIX passes Exporter some very memory hungry data structures.
e50bb9a1 124
eed36644
NC
125=head2 embed.pl/makedef.pl
126
127There is a script F<embed.pl> that generates several header files to prefix
128all of Perl's symbols in a consistent way, to provide some semblance of
129namespace support in C<C>. Functions are declared in F<embed.fnc>, variables
907b3e23 130in F<interpvar.h>. Quite a few of the functions and variables
eed36644
NC
131are conditionally declared there, using C<#ifdef>. However, F<embed.pl>
132doesn't understand the C macros, so the rules about which symbols are present
133when is duplicated in F<makedef.pl>. Writing things twice is bad, m'kay.
134It would be good to teach C<embed.pl> to understand the conditional
135compilation, and hence remove the duplication, and the mistakes it has caused.
e50bb9a1 136
801de10e
NC
137=head2 use strict; and AutoLoad
138
139Currently if you write
140
141 package Whack;
142 use AutoLoader 'AUTOLOAD';
143 use strict;
144 1;
145 __END__
146 sub bloop {
147 print join (' ', No, strict, here), "!\n";
148 }
149
150then C<use strict;> isn't in force within the autoloaded subroutines. It would
151be more consistent (and less surprising) to arrange for all lexical pragmas
152in force at the __END__ block to be in force within each autoloaded subroutine.
153
773b3597
RGS
154There's a similar problem with SelfLoader.
155
0bdfc961 156=head1 Tasks that need a little sysadmin-type knowledge
e50bb9a1 157
0bdfc961
NC
158Or if you prefer, tasks that you would learn from, and broaden your skills
159base...
e50bb9a1 160
cd793d32 161=head2 make HTML install work
e50bb9a1 162
adebf063
NC
163There is an C<installhtml> target in the Makefile. It's marked as
164"experimental". It would be good to get this tested, make it work reliably, and
165remove the "experimental" tag. This would include
166
167=over 4
168
169=item 1
170
171Checking that cross linking between various parts of the documentation works.
172In particular that links work between the modules (files with POD in F<lib/>)
173and the core documentation (files in F<pod/>)
174
175=item 2
176
617eabfa
NC
177Work out how to split C<perlfunc> into chunks, preferably one per function
178group, preferably with general case code that could be used elsewhere.
179Challenges here are correctly identifying the groups of functions that go
180together, and making the right named external cross-links point to the right
181page. Things to be aware of are C<-X>, groups such as C<getpwnam> to
182C<endservent>, two or more C<=items> giving the different parameter lists, such
183as
adebf063
NC
184
185 =item substr EXPR,OFFSET,LENGTH,REPLACEMENT
adebf063 186 =item substr EXPR,OFFSET,LENGTH
adebf063
NC
187 =item substr EXPR,OFFSET
188
189and different parameter lists having different meanings. (eg C<select>)
190
191=back
3a89a73c 192
0bdfc961
NC
193=head2 compressed man pages
194
195Be able to install them. This would probably need a configure test to see how
196the system does compressed man pages (same directory/different directory?
197same filename/different filename), as well as tweaking the F<installman> script
198to compress as necessary.
199
30222c0f
NC
200=head2 Add a code coverage target to the Makefile
201
202Make it easy for anyone to run Devel::Cover on the core's tests. The steps
203to do this manually are roughly
204
205=over 4
206
207=item *
208
209do a normal C<Configure>, but include Devel::Cover as a module to install
210(see F<INSTALL> for how to do this)
211
212=item *
213
214 make perl
215
216=item *
217
218 cd t; HARNESS_PERL_SWITCHES=-MDevel::Cover ./perl -I../lib harness
219
220=item *
221
222Process the resulting Devel::Cover database
223
224=back
225
226This just give you the coverage of the F<.pm>s. To also get the C level
227coverage you need to
228
229=over 4
230
231=item *
232
233Additionally tell C<Configure> to use the appropriate C compiler flags for
234C<gcov>
235
236=item *
237
238 make perl.gcov
239
240(instead of C<make perl>)
241
242=item *
243
244After running the tests run C<gcov> to generate all the F<.gcov> files.
245(Including down in the subdirectories of F<ext/>
246
247=item *
248
249(From the top level perl directory) run C<gcov2perl> on all the C<.gcov> files
250to get their stats into the cover_db directory.
251
252=item *
253
254Then process the Devel::Cover database
255
256=back
257
258It would be good to add a single switch to C<Configure> to specify that you
259wanted to perform perl level coverage, and another to specify C level
260coverage, and have C<Configure> and the F<Makefile> do all the right things
261automatically.
262
02f21748 263=head2 Make Config.pm cope with differences between built and installed perl
0bdfc961
NC
264
265Quite often vendors ship a perl binary compiled with their (pay-for)
266compilers. People install a free compiler, such as gcc. To work out how to
267build extensions, Perl interrogates C<%Config>, so in this situation
268C<%Config> describes compilers that aren't there, and extension building
269fails. This forces people into choosing between re-compiling perl themselves
270using the compiler they have, or only using modules that the vendor ships.
271
272It would be good to find a way teach C<Config.pm> about the installation setup,
273possibly involving probing at install time or later, so that the C<%Config> in
274a binary distribution better describes the installed machine, when the
275installed machine differs from the build machine in some significant way.
276
728f4ecd
NC
277=head2 linker specification files
278
279Some platforms mandate that you provide a list of a shared library's external
280symbols to the linker, so the core already has the infrastructure in place to
281do this for generating shared perl libraries. My understanding is that the
282GNU toolchain can accept an optional linker specification file, and restrict
283visibility just to symbols declared in that file. It would be good to extend
284F<makedef.pl> to support this format, and to provide a means within
285C<Configure> to enable it. This would allow Unix users to test that the
286export list is correct, and to build a perl that does not pollute the global
287namespace with private symbols.
288
a229ae3b
RGS
289=head2 Cross-compile support
290
291Currently C<Configure> understands C<-Dusecrosscompile> option. This option
292arranges for building C<miniperl> for TARGET machine, so this C<miniperl> is
293assumed then to be copied to TARGET machine and used as a replacement of full
294C<perl> executable.
295
d1307786 296This could be done little differently. Namely C<miniperl> should be built for
a229ae3b 297HOST and then full C<perl> with extensions should be compiled for TARGET.
d1307786 298This, however, might require extra trickery for %Config: we have one config
87a942b1
JH
299first for HOST and then another for TARGET. Tools like MakeMaker will be
300mightily confused. Having around two different types of executables and
301libraries (HOST and TARGET) makes life interesting for Makefiles and
302shell (and Perl) scripts. There is $Config{run}, normally empty, which
303can be used as an execution wrapper. Also note that in some
304cross-compilation/execution environments the HOST and the TARGET do
305not see the same filesystem(s), the $Config{run} may need to do some
306file/directory copying back and forth.
0bdfc961
NC
307
308=head1 Tasks that need a little C knowledge
309
310These tasks would need a little C knowledge, but don't need any specific
311background or experience with XS, or how the Perl interpreter works
312
313=head2 Make it clear from -v if this is the exact official release
89007cb3 314
617eabfa
NC
315Currently perl from C<p4>/C<rsync> ships with a F<patchlevel.h> file that
316usually defines one local patch, of the form "MAINT12345" or "RC1". The output
317of perl -v doesn't report that a perl isn't an official release, and this
89007cb3 318information can get lost in bugs reports. Because of this, the minor version
fa11829f 319isn't bumped up until RC time, to minimise the possibility of versions of perl
89007cb3
NC
320escaping that believe themselves to be newer than they actually are.
321
322It would be useful to find an elegant way to have the "this is an interim
323maintenance release" or "this is a release candidate" in the terse -v output,
324and have it so that it's easy for the pumpking to remove this just as the
325release tarball is rolled up. This way the version pulled out of rsync would
326always say "I'm a development release" and it would be safe to bump the
327reported minor version as soon as a release ships, which would aid perl
328developers.
329
0bdfc961
NC
330This task is really about thinking of an elegant way to arrange the C source
331such that it's trivial for the Pumpking to flag "this is an official release"
332when making a tarball, yet leave the default source saying "I'm not the
333official release".
334
fee0a0f7 335=head2 Profile Perl - am I hot or not?
62403a3c 336
fee0a0f7
NC
337The Perl source code is stable enough that it makes sense to profile it,
338identify and optimise the hotspots. It would be good to measure the
339performance of the Perl interpreter using free tools such as cachegrind,
340gprof, and dtrace, and work to reduce the bottlenecks they reveal.
341
342As part of this, the idea of F<pp_hot.c> is that it contains the I<hot> ops,
343the ops that are most commonly used. The idea is that by grouping them, their
344object code will be adjacent in the executable, so they have a greater chance
345of already being in the CPU cache (or swapped in) due to being near another op
346already in use.
62403a3c
NC
347
348Except that it's not clear if these really are the most commonly used ops. So
fee0a0f7
NC
349as part of exercising your skills with coverage and profiling tools you might
350want to determine what ops I<really> are the most commonly used. And in turn
351suggest evictions and promotions to achieve a better F<pp_hot.c>.
62403a3c 352
98fed0ad
NC
353=head2 Allocate OPs from arenas
354
355Currently all new OP structures are individually malloc()ed and free()d.
356All C<malloc> implementations have space overheads, and are now as fast as
357custom allocates so it would both use less memory and less CPU to allocate
358the various OP structures from arenas. The SV arena code can probably be
359re-used for this.
360
a229ae3b 361=head2 Improve win32/wince.c
0bdfc961 362
a229ae3b 363Currently, numerous functions look virtually, if not completely,
02f21748 364identical in both C<win32/wince.c> and C<win32/win32.c> files, which can't
6d71adcd
NC
365be good.
366
c5b31784
SH
367=head2 Use secure CRT functions when building with VC8 on Win32
368
369Visual C++ 2005 (VC++ 8.x) deprecated a number of CRT functions on the basis
370that they were "unsafe" and introduced differently named secure versions of
371them as replacements, e.g. instead of writing
372
373 FILE* f = fopen(__FILE__, "r");
374
375one should now write
376
377 FILE* f;
378 errno_t err = fopen_s(&f, __FILE__, "r");
379
380Currently, the warnings about these deprecations have been disabled by adding
381-D_CRT_SECURE_NO_DEPRECATE to the CFLAGS. It would be nice to remove that
382warning suppressant and actually make use of the new secure CRT functions.
383
384There is also a similar issue with POSIX CRT function names like fileno having
385been deprecated in favour of ISO C++ conformant names like _fileno. These
386warnings are also currently suppressed with the compiler option /wd4996. It
387might be nice to do as Microsoft suggest here too, although, unlike the secure
388functions issue, there is presumably little or no benefit in this case.
389
6d71adcd
NC
390=head1 Tasks that need a knowledge of XS
391
392These tasks would need C knowledge, and roughly the level of knowledge of
393the perl API that comes from writing modules that use XS to interface to
394C.
395
6d71adcd
NC
396=head2 autovivification
397
398Make all autovivification consistent w.r.t LVALUE/RVALUE and strict/no strict;
399
400This task is incremental - even a little bit of work on it will help.
401
402=head2 Unicode in Filenames
403
404chdir, chmod, chown, chroot, exec, glob, link, lstat, mkdir, open,
405opendir, qx, readdir, readlink, rename, rmdir, stat, symlink, sysopen,
406system, truncate, unlink, utime, -X. All these could potentially accept
407Unicode filenames either as input or output (and in the case of system
408and qx Unicode in general, as input or output to/from the shell).
409Whether a filesystem - an operating system pair understands Unicode in
410filenames varies.
411
412Known combinations that have some level of understanding include
413Microsoft NTFS, Apple HFS+ (In Mac OS 9 and X) and Apple UFS (in Mac
414OS X), NFS v4 is rumored to be Unicode, and of course Plan 9. How to
415create Unicode filenames, what forms of Unicode are accepted and used
416(UCS-2, UTF-16, UTF-8), what (if any) is the normalization form used,
417and so on, varies. Finding the right level of interfacing to Perl
418requires some thought. Remember that an OS does not implicate a
419filesystem.
420
421(The Windows -C command flag "wide API support" has been at least
422temporarily retired in 5.8.1, and the -C has been repurposed, see
423L<perlrun>.)
424
87a942b1
JH
425Most probably the right way to do this would be this:
426L</"Virtualize operating system access">.
427
6d71adcd
NC
428=head2 Unicode in %ENV
429
430Currently the %ENV entries are always byte strings.
87a942b1 431See L</"Virtualize operating system access">.
6d71adcd 432
1f2e7916
JD
433=head2 Unicode and glob()
434
435Currently glob patterns and filenames returned from File::Glob::glob()
87a942b1 436are always byte strings. See L</"Virtualize operating system access">.
1f2e7916 437
6d71adcd
NC
438=head2 use less 'memory'
439
440Investigate trade offs to switch out perl's choices on memory usage.
441Particularly perl should be able to give memory back.
442
443This task is incremental - even a little bit of work on it will help.
444
445=head2 Re-implement C<:unique> in a way that is actually thread-safe
446
447The old implementation made bad assumptions on several levels. A good 90%
448solution might be just to make C<:unique> work to share the string buffer
449of SvPVs. That way large constant strings can be shared between ithreads,
450such as the configuration information in F<Config>.
451
452=head2 Make tainting consistent
453
454Tainting would be easier to use if it didn't take documented shortcuts and
455allow taint to "leak" everywhere within an expression.
456
457=head2 readpipe(LIST)
458
459system() accepts a LIST syntax (and a PROGRAM LIST syntax) to avoid
460running a shell. readpipe() (the function behind qx//) could be similarly
461extended.
462
463=head2 strcat(), strcpy(), strncat(), strncpy(), sprintf(), vsprintf()
464
465Maybe create a utility that checks after each libperl.a creation that
466none of the above (nor sprintf(), vsprintf(), or *SHUDDER* gets())
467ever creep back to libperl.a.
468
469 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)$/'
470
471Note, of course, that this will only tell whether B<your> platform
472is using those naughty interfaces.
473
474=head2 Audit the code for destruction ordering assumptions
475
476Change 25773 notes
477
478 /* Need to check SvMAGICAL, as during global destruction it may be that
479 AvARYLEN(av) has been freed before av, and hence the SvANY() pointer
480 is now part of the linked list of SV heads, rather than pointing to
481 the original body. */
482 /* FIXME - audit the code for other bugs like this one. */
483
484adding the C<SvMAGICAL> check to
485
486 if (AvARYLEN(av) && SvMAGICAL(AvARYLEN(av))) {
487 MAGIC *mg = mg_find (AvARYLEN(av), PERL_MAGIC_arylen);
488
489Go through the core and look for similar assumptions that SVs have particular
490types, as all bets are off during global destruction.
491
749904bf
JH
492=head2 Extend PerlIO and PerlIO::Scalar
493
494PerlIO::Scalar doesn't know how to truncate(). Implementing this
495would require extending the PerlIO vtable.
496
497Similarly the PerlIO vtable doesn't know about formats (write()), or
498about stat(), or chmod()/chown(), utime(), or flock().
499
500(For PerlIO::Scalar it's hard to see what e.g. mode bits or ownership
501would mean.)
502
503PerlIO doesn't do directories or symlinks, either: mkdir(), rmdir(),
504opendir(), closedir(), seekdir(), rewinddir(), glob(); symlink(),
505readlink().
506
94da6c29
JH
507See also L</"Virtualize operating system access">.
508
3236f110
NC
509=head2 -C on the #! line
510
511It should be possible to make -C work correctly if found on the #! line,
512given that all perl command line options are strict ASCII, and -C changes
513only the interpretation of non-ASCII characters, and not for the script file
514handle. To make it work needs some investigation of the ordering of function
515calls during startup, and (by implication) a bit of tweaking of that order.
516
517
0bdfc961 518=head1 Tasks that need a knowledge of the interpreter
3298bd4d 519
0bdfc961
NC
520These tasks would need C knowledge, and knowledge of how the interpreter works,
521or a willingness to learn.
3298bd4d 522
4fedb12c
RGS
523=head2 Implement $value ~~ 0 .. $range
524
525It would be nice to extend the syntax of the C<~~> operator to also
526understand numeric (and maybe alphanumeric) ranges.
a393eb28
RGS
527
528=head2 A does() built-in
529
530Like ref(), only useful. It would call the C<DOES> method on objects; it
531would also tell whether something can be dereferenced as an
532array/hash/etc., or used as a regexp, etc.
533L<http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2007-03/msg00481.html>
534
535=head2 Tied filehandles and write() don't mix
536
537There is no method on tied filehandles to allow them to be called back by
538formats.
4fedb12c 539
d10fc472 540=head2 Attach/detach debugger from running program
1626a787 541
cd793d32
NC
542The old perltodo notes "With C<gdb>, you can attach the debugger to a running
543program if you pass the process ID. It would be good to do this with the Perl
0bdfc961
NC
544debugger on a running Perl program, although I'm not sure how it would be
545done." ssh and screen do this with named pipes in /tmp. Maybe we can too.
1626a787 546
0bdfc961
NC
547=head2 LVALUE functions for lists
548
549The old perltodo notes that lvalue functions don't work for list or hash
550slices. This would be good to fix.
551
552=head2 LVALUE functions in the debugger
553
554The old perltodo notes that lvalue functions don't work in the debugger. This
555would be good to fix.
556
0bdfc961
NC
557=head2 regexp optimiser optional
558
559The regexp optimiser is not optional. It should configurable to be, to allow
560its performance to be measured, and its bugs to be easily demonstrated.
561
02f21748
RGS
562=head2 delete &function
563
564Allow to delete functions. One can already undef them, but they're still
565in the stash.
566
ef36c6a7
RGS
567=head2 C</w> regex modifier
568
569That flag would enable to match whole words, and also to interpolate
570arrays as alternations. With it, C</P/w> would be roughly equivalent to:
571
572 do { local $"='|'; /\b(?:P)\b/ }
573
574See L<http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2007-01/msg00400.html>
575for the discussion.
576
0bdfc961
NC
577=head2 optional optimizer
578
579Make the peephole optimizer optional. Currently it performs two tasks as
580it walks the optree - genuine peephole optimisations, and necessary fixups of
581ops. It would be good to find an efficient way to switch out the
582optimisations whilst keeping the fixups.
583
584=head2 You WANT *how* many
585
586Currently contexts are void, scalar and list. split has a special mechanism in
587place to pass in the number of return values wanted. It would be useful to
588have a general mechanism for this, backwards compatible and little speed hit.
589This would allow proposals such as short circuiting sort to be implemented
590as a module on CPAN.
591
592=head2 lexical aliases
593
594Allow lexical aliases (maybe via the syntax C<my \$alias = \$foo>.
595
596=head2 entersub XS vs Perl
597
598At the moment pp_entersub is huge, and has code to deal with entering both
599perl and XS subroutines. Subroutine implementations rarely change between
600perl and XS at run time, so investigate using 2 ops to enter subs (one for
601XS, one for perl) and swap between if a sub is redefined.
2810d901
NC
602
603=head2 Self ties
604
605self ties are currently illegal because they caused too many segfaults. Maybe
606the causes of these could be tracked down and self-ties on all types re-
607instated.
0bdfc961
NC
608
609=head2 Optimize away @_
610
611The old perltodo notes "Look at the "reification" code in C<av.c>".
612
16fc99ce
NC
613=head2 Properly Unicode safe tokeniser and pads.
614
615The tokeniser isn't actually very UTF-8 clean. C<use utf8;> is a hack -
616variable names are stored in stashes as raw bytes, without the utf-8 flag
617set. The pad API only takes a C<char *> pointer, so that's all bytes too. The
618tokeniser ignores the UTF-8-ness of C<PL_rsfp>, or any SVs returned from
619source filters. All this could be fixed.
620
f092b1f4
RGS
621=head2 The yada yada yada operators
622
623Perl 6's Synopsis 3 says:
624
625I<The ... operator is the "yada, yada, yada" list operator, which is used as
626the body in function prototypes. It complains bitterly (by calling fail)
627if it is ever executed. Variant ??? calls warn, and !!! calls die.>
628
629Those would be nice to add to Perl 5. That could be done without new ops.
630
87a942b1
JH
631=head2 Virtualize operating system access
632
633Implement a set of "vtables" that virtualizes operating system access
634(open(), mkdir(), unlink(), readdir(), getenv(), etc.) At the very
635least these interfaces should take SVs as "name" arguments instead of
636bare char pointers; probably the most flexible and extensible way
e1a3d5d1
JH
637would be for the Perl-facing interfaces to accept HVs. The system
638needs to be per-operating-system and per-file-system
639hookable/filterable, preferably both from XS and Perl level
87a942b1
JH
640(L<perlport/"Files and Filesystems"> is good reading at this point,
641in fact, all of L<perlport> is.)
642
e1a3d5d1
JH
643This has actually already been implemented (but only for Win32),
644take a look at F<iperlsys.h> and F<win32/perlhost.h>. While all Win32
645variants go through a set of "vtables" for operating system access,
646non-Win32 systems currently go straight for the POSIX/UNIX-style
647system/library call. Similar system as for Win32 should be
648implemented for all platforms. The existing Win32 implementation
649probably does not need to survive alongside this proposed new
650implementation, the approaches could be merged.
87a942b1
JH
651
652What would this give us? One often-asked-for feature this would
94da6c29
JH
653enable is using Unicode for filenames, and other "names" like %ENV,
654usernames, hostnames, and so forth.
655(See L<perlunicode/"When Unicode Does Not Happen">.)
656
657But this kind of virtualization would also allow for things like
658virtual filesystems, virtual networks, and "sandboxes" (though as long
659as dynamic loading of random object code is allowed, not very safe
660sandboxes since external code of course know not of Perl's vtables).
661An example of a smaller "sandbox" is that this feature can be used to
662implement per-thread working directories: Win32 already does this.
663
664See also L</"Extend PerlIO and PerlIO::Scalar">.
87a942b1 665
0bdfc961
NC
666=head1 Big projects
667
668Tasks that will get your name mentioned in the description of the "Highlights
87a942b1 669of 5.12"
0bdfc961
NC
670
671=head2 make ithreads more robust
672
4e577f8b 673Generally make ithreads more robust. See also L</iCOW>
0bdfc961
NC
674
675This task is incremental - even a little bit of work on it will help, and
676will be greatly appreciated.
677
6c047da7
YST
678One bit would be to write the missing code in sv.c:Perl_dirp_dup.
679
59c7f7d5
RGS
680Fix Perl_sv_dup, et al so that threads can return objects.
681
0bdfc961
NC
682=head2 iCOW
683
684Sarathy and Arthur have a proposal for an improved Copy On Write which
685specifically will be able to COW new ithreads. If this can be implemented
686it would be a good thing.
687
688=head2 (?{...}) closures in regexps
689
690Fix (or rewrite) the implementation of the C</(?{...})/> closures.
691
692=head2 A re-entrant regexp engine
693
694This will allow the use of a regex from inside (?{ }), (??{ }) and
695(?(?{ })|) constructs.
6bda09f9 696
6bda09f9
YO
697=head2 Add class set operations to regexp engine
698
699Apparently these are quite useful. Anyway, Jeffery Friedl wants them.
700
701demerphq has this on his todo list, but right at the bottom.