Commit | Line | Data |
---|---|---|
7711098a GS |
1 | =head1 NAME |
2 | ||
3 | perltodo - Perl TO-DO List | |
4 | ||
5 | =head1 DESCRIPTION | |
e50bb9a1 | 6 | |
0bdfc961 NC |
7 | This is a list of wishes for Perl. The tasks we think are smaller or easier |
8 | are listed first. Anyone is welcome to work on any of these, but it's a good | |
9 | idea to first contact I<perl5-porters@perl.org> to avoid duplication of | |
10 | effort. By all means contact a pumpking privately first if you prefer. | |
e50bb9a1 | 11 | |
0bdfc961 NC |
12 | Whilst patches to make the list shorter are most welcome, ideas to add to |
13 | the list are also encouraged. Check the perl5-porters archives for past | |
14 | ideas, 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 | |
938c8732 | 18 | |
938c8732 | 19 | |
938c8732 | 20 | |
e50bb9a1 | 21 | |
0bdfc961 | 22 | =head1 Tasks that only need Perl knowledge |
e50bb9a1 | 23 | |
0bdfc961 | 24 | =head2 common test code for timed bail out |
e50bb9a1 | 25 | |
0bdfc961 NC |
26 | Write portable self destruct code for tests to stop them burning CPU in |
27 | infinite loops. This needs to avoid using alarm, as some of the tests are | |
28 | testing alarm/sleep or timers. | |
e50bb9a1 | 29 | |
0bdfc961 | 30 | =head2 POD -> HTML conversion in the core still sucks |
e50bb9a1 | 31 | |
938c8732 | 32 | Which is crazy given just how simple POD purports to be, and how simple HTML |
adebf063 NC |
33 | can be. It's not actually I<as> simple as it sounds, particularly with the |
34 | flexibility POD allows for C<=item>, but it would be good to improve the | |
35 | visual appeal of the HTML generated, and to avoid it having any validation | |
36 | errors. See also L</make HTML install work>, as the layout of installation tree | |
37 | is needed to improve the cross-linking. | |
938c8732 | 38 | |
0bdfc961 | 39 | =head2 Make Schwern poorer |
e50bb9a1 | 40 | |
0bdfc961 NC |
41 | We should have for everything. When all the core's modules are tested, |
42 | Schwern has promised to donate to $500 to TPF. We may need volunteers to | |
43 | hold him upside down and shake vigorously in order to actually extract the | |
44 | cash. | |
3958b146 | 45 | |
0bdfc961 | 46 | See F<t/lib/1_compile.t> for the 3 remaining modules that need tests. |
e50bb9a1 | 47 | |
0bdfc961 | 48 | =head2 Improve the coverage of the core tests |
e50bb9a1 | 49 | |
0bdfc961 NC |
50 | Use Devel::Cover to ascertain the core's test coverage, then add tests that |
51 | are currently missing. | |
30222c0f | 52 | |
0bdfc961 | 53 | =head2 test B |
e50bb9a1 | 54 | |
0bdfc961 | 55 | A full test suite for the B module would be nice. |
e50bb9a1 | 56 | |
0bdfc961 | 57 | =head2 A decent benchmark |
e50bb9a1 | 58 | |
0bdfc961 NC |
59 | perlbench seems impervious to any recent changes made to the perl core. It |
60 | would be useful to have a reasonable general benchmarking suite that roughly | |
61 | represented what current perl programs do, and measurably reported whether | |
62 | tweaks to the core improve, degrade or don't really affect performance, to | |
63 | guide people attempting to optimise the guts of perl. Gisle would welcome | |
64 | new tests for perlbench. | |
6168cf99 | 65 | |
0bdfc961 | 66 | =head2 fix tainting bugs |
6168cf99 | 67 | |
0bdfc961 NC |
68 | Fix the bugs revealed by running the test suite with the C<-t> switch (via |
69 | C<make test.taintwarn>). | |
e50bb9a1 | 70 | |
0bdfc961 | 71 | =head2 Dual life everything |
e50bb9a1 | 72 | |
0bdfc961 NC |
73 | As part of the "dists" plan, anything that doesn't belong in the smallest perl |
74 | distribution needs to be dual lifed. Anything else can be too. Figure out what | |
75 | changes would be needed to package that module and its tests up for CPAN, and | |
76 | do so. Test it with older perl releases, and fix the problems you find. | |
e50bb9a1 | 77 | |
0bdfc961 | 78 | =head2 Improving C<threads::shared> |
722d2a37 | 79 | |
0bdfc961 NC |
80 | Investigate whether C<threads::shared> could share aggregates properly with |
81 | only Perl level changes to shared.pm | |
722d2a37 | 82 | |
0bdfc961 | 83 | =head2 POSIX memory footprint |
e50bb9a1 | 84 | |
0bdfc961 NC |
85 | Ilya observed that use POSIX; eats memory like there's no tomorrow, and at |
86 | various times worked to cut it down. There is probably still fat to cut out - | |
87 | for example POSIX passes Exporter some very memory hungry data structures. | |
e50bb9a1 | 88 | |
e50bb9a1 | 89 | |
e50bb9a1 | 90 | |
e50bb9a1 | 91 | |
e50bb9a1 | 92 | |
adebf063 | 93 | |
adebf063 | 94 | |
0bdfc961 | 95 | =head1 Tasks that need a little sysadmin-type knowledge |
e50bb9a1 | 96 | |
0bdfc961 NC |
97 | Or if you prefer, tasks that you would learn from, and broaden your skills |
98 | base... | |
e50bb9a1 | 99 | |
cd793d32 | 100 | =head2 make HTML install work |
e50bb9a1 | 101 | |
adebf063 NC |
102 | There is an C<installhtml> target in the Makefile. It's marked as |
103 | "experimental". It would be good to get this tested, make it work reliably, and | |
104 | remove the "experimental" tag. This would include | |
105 | ||
106 | =over 4 | |
107 | ||
108 | =item 1 | |
109 | ||
110 | Checking that cross linking between various parts of the documentation works. | |
111 | In particular that links work between the modules (files with POD in F<lib/>) | |
112 | and the core documentation (files in F<pod/>) | |
113 | ||
114 | =item 2 | |
115 | ||
116 | Work out how to split perlfunc into chunks, preferably one per function group, | |
117 | preferably with general case code that could be used elsewhere. Challenges | |
118 | here are correctly identifying the groups of functions that go together, and | |
119 | making the right named external cross-links point to the right page. Things to | |
120 | be aware of are C<-X>, groups such as C<getpwnam> to C<endservent>, two or | |
121 | more C<=items> giving the different parameter lists, such as | |
122 | ||
123 | =item substr EXPR,OFFSET,LENGTH,REPLACEMENT | |
124 | ||
125 | =item substr EXPR,OFFSET,LENGTH | |
126 | ||
127 | =item substr EXPR,OFFSET | |
128 | ||
129 | and different parameter lists having different meanings. (eg C<select>) | |
130 | ||
131 | =back | |
3a89a73c | 132 | |
0bdfc961 NC |
133 | =head2 compressed man pages |
134 | ||
135 | Be able to install them. This would probably need a configure test to see how | |
136 | the system does compressed man pages (same directory/different directory? | |
137 | same filename/different filename), as well as tweaking the F<installman> script | |
138 | to compress as necessary. | |
139 | ||
30222c0f NC |
140 | =head2 Add a code coverage target to the Makefile |
141 | ||
142 | Make it easy for anyone to run Devel::Cover on the core's tests. The steps | |
143 | to do this manually are roughly | |
144 | ||
145 | =over 4 | |
146 | ||
147 | =item * | |
148 | ||
149 | do a normal C<Configure>, but include Devel::Cover as a module to install | |
150 | (see F<INSTALL> for how to do this) | |
151 | ||
152 | =item * | |
153 | ||
154 | make perl | |
155 | ||
156 | =item * | |
157 | ||
158 | cd t; HARNESS_PERL_SWITCHES=-MDevel::Cover ./perl -I../lib harness | |
159 | ||
160 | =item * | |
161 | ||
162 | Process the resulting Devel::Cover database | |
163 | ||
164 | =back | |
165 | ||
166 | This just give you the coverage of the F<.pm>s. To also get the C level | |
167 | coverage you need to | |
168 | ||
169 | =over 4 | |
170 | ||
171 | =item * | |
172 | ||
173 | Additionally tell C<Configure> to use the appropriate C compiler flags for | |
174 | C<gcov> | |
175 | ||
176 | =item * | |
177 | ||
178 | make perl.gcov | |
179 | ||
180 | (instead of C<make perl>) | |
181 | ||
182 | =item * | |
183 | ||
184 | After running the tests run C<gcov> to generate all the F<.gcov> files. | |
185 | (Including down in the subdirectories of F<ext/> | |
186 | ||
187 | =item * | |
188 | ||
189 | (From the top level perl directory) run C<gcov2perl> on all the C<.gcov> files | |
190 | to get their stats into the cover_db directory. | |
191 | ||
192 | =item * | |
193 | ||
194 | Then process the Devel::Cover database | |
195 | ||
196 | =back | |
197 | ||
198 | It would be good to add a single switch to C<Configure> to specify that you | |
199 | wanted to perform perl level coverage, and another to specify C level | |
200 | coverage, and have C<Configure> and the F<Makefile> do all the right things | |
201 | automatically. | |
202 | ||
0bdfc961 NC |
203 | =head2 Make Config.pm cope with differences between build and installed perl |
204 | ||
205 | Quite often vendors ship a perl binary compiled with their (pay-for) | |
206 | compilers. People install a free compiler, such as gcc. To work out how to | |
207 | build extensions, Perl interrogates C<%Config>, so in this situation | |
208 | C<%Config> describes compilers that aren't there, and extension building | |
209 | fails. This forces people into choosing between re-compiling perl themselves | |
210 | using the compiler they have, or only using modules that the vendor ships. | |
211 | ||
212 | It would be good to find a way teach C<Config.pm> about the installation setup, | |
213 | possibly involving probing at install time or later, so that the C<%Config> in | |
214 | a binary distribution better describes the installed machine, when the | |
215 | installed machine differs from the build machine in some significant way. | |
216 | ||
217 | =head2 Relocatable perl | |
218 | ||
219 | The C level patches needed to create a relocatable perl binary are done, as | |
220 | is the work on Config.pm. All that's left to do is the C<Configure> tweaking | |
221 | to let people specify how they want to do the install. | |
222 | ||
46925299 | 223 | =head2 make parallel builds work |
0bdfc961 | 224 | |
46925299 NC |
225 | Currently parallel builds (such as C<make -j3>) don't work reliably. We believe |
226 | that this is due to incomplete dependency specification in the F<Makefile>. | |
227 | It would be good if someone were able to track down the causes of these | |
228 | problems, so that parallel builds worked properly. | |
0bdfc961 NC |
229 | |
230 | ||
231 | ||
232 | =head1 Tasks that need a little C knowledge | |
233 | ||
234 | These tasks would need a little C knowledge, but don't need any specific | |
235 | background or experience with XS, or how the Perl interpreter works | |
236 | ||
237 | =head2 Make it clear from -v if this is the exact official release | |
89007cb3 NC |
238 | |
239 | Currently perl from p4/rsync ships with a patchlevel.h file that usually | |
240 | defines one local patch, of the form "MAINT12345" or "RC1". The output of | |
241 | perl -v doesn't report that a perl isn't an official release, and this | |
242 | information can get lost in bugs reports. Because of this, the minor version | |
fa11829f | 243 | isn't bumped up until RC time, to minimise the possibility of versions of perl |
89007cb3 NC |
244 | escaping that believe themselves to be newer than they actually are. |
245 | ||
246 | It would be useful to find an elegant way to have the "this is an interim | |
247 | maintenance release" or "this is a release candidate" in the terse -v output, | |
248 | and have it so that it's easy for the pumpking to remove this just as the | |
249 | release tarball is rolled up. This way the version pulled out of rsync would | |
250 | always say "I'm a development release" and it would be safe to bump the | |
251 | reported minor version as soon as a release ships, which would aid perl | |
252 | developers. | |
253 | ||
0bdfc961 NC |
254 | This task is really about thinking of an elegant way to arrange the C source |
255 | such that it's trivial for the Pumpking to flag "this is an official release" | |
256 | when making a tarball, yet leave the default source saying "I'm not the | |
257 | official release". | |
258 | ||
259 | =head2 bincompat functions | |
260 | ||
261 | There are lots of functions which are retained for binary compatibility. | |
262 | Clean these up. Move them to mathom.c, and don't compile for blead? | |
263 | ||
62403a3c NC |
264 | =head2 am I hot or not? |
265 | ||
266 | The idea of F<pp_hot.c> is that it contains the I<hot> ops, the ops that are | |
267 | most commonly used. The idea is that by grouping them, their object code will | |
268 | be adjacent in the executable, so they have a greater chance of already being | |
269 | in the CPU cache (or swapped in) due to being near another op already in use. | |
270 | ||
271 | Except that it's not clear if these really are the most commonly used ops. So | |
272 | anyone feeling like exercising their skill with coverage and profiling tools | |
273 | might want to determine what ops I<really> are the most commonly used. And in | |
274 | turn suggest evictions and promotions to achieve a better F<pp_hot.c>. | |
275 | ||
276 | ||
0bdfc961 NC |
277 | |
278 | ||
279 | ||
0bdfc961 | 280 | =head1 Tasks that need a knowledge of XS |
e50bb9a1 | 281 | |
0bdfc961 NC |
282 | These tasks would need C knowledge, and roughly the level of knowledge of |
283 | the perl API that comes from writing modules that use XS to interface to | |
284 | C. | |
285 | ||
286 | =head2 IPv6 | |
287 | ||
288 | Clean this up. Check everything in core works | |
289 | ||
e593da1a NC |
290 | =head2 merge Perl_sv_2[inpu]v |
291 | ||
292 | There's a lot of code shared between C<Perl_sv_2iv_flags>, | |
293 | C<Perl_sv_2uv_flags>, C<Perl_sv_2nv>, and C<Perl_sv_2pv_flags>. It would be | |
294 | interesting to see if some of it can be merged into common shared static | |
295 | functions. In particular, C<Perl_sv_2uv_flags> started out as a cut&paste | |
296 | from C<Perl_sv_2iv_flags> around 5.005_50 time, and it may be possible to | |
297 | replace both with a single function that returns a value or union which is | |
298 | split out by the macros in F<sv.h> | |
299 | ||
0bdfc961 NC |
300 | =head2 UTF8 caching code |
301 | ||
302 | The string position/offset cache is not optional. It should be. | |
303 | ||
304 | =head2 Implicit Latin 1 => Unicode translation | |
305 | ||
306 | Conversions from byte strings to UTF-8 currently map high bit characters | |
307 | to Unicode without translation (or, depending on how you look at it, by | |
308 | implicitly assuming that the byte strings are in Latin-1). As perl assumes | |
309 | the C locale by default, upgrading a string to UTF-8 may change the | |
310 | meaning of its contents regarding character classes, case mapping, etc. | |
311 | This should probably emit a warning (at least). | |
312 | ||
313 | This task is incremental - even a little bit of work on it will help. | |
e50bb9a1 | 314 | |
cd793d32 | 315 | =head2 autovivification |
e50bb9a1 | 316 | |
cd793d32 | 317 | Make all autovivification consistent w.r.t LVALUE/RVALUE and strict/no strict; |
e50bb9a1 | 318 | |
0bdfc961 | 319 | This task is incremental - even a little bit of work on it will help. |
e50bb9a1 | 320 | |
0bdfc961 | 321 | =head2 Unicode in Filenames |
e50bb9a1 | 322 | |
0bdfc961 NC |
323 | chdir, chmod, chown, chroot, exec, glob, link, lstat, mkdir, open, |
324 | opendir, qx, readdir, readlink, rename, rmdir, stat, symlink, sysopen, | |
325 | system, truncate, unlink, utime, -X. All these could potentially accept | |
326 | Unicode filenames either as input or output (and in the case of system | |
327 | and qx Unicode in general, as input or output to/from the shell). | |
328 | Whether a filesystem - an operating system pair understands Unicode in | |
329 | filenames varies. | |
e50bb9a1 | 330 | |
0bdfc961 NC |
331 | Known combinations that have some level of understanding include |
332 | Microsoft NTFS, Apple HFS+ (In Mac OS 9 and X) and Apple UFS (in Mac | |
333 | OS X), NFS v4 is rumored to be Unicode, and of course Plan 9. How to | |
334 | create Unicode filenames, what forms of Unicode are accepted and used | |
335 | (UCS-2, UTF-16, UTF-8), what (if any) is the normalization form used, | |
336 | and so on, varies. Finding the right level of interfacing to Perl | |
337 | requires some thought. Remember that an OS does not implicate a | |
338 | filesystem. | |
e50bb9a1 | 339 | |
0bdfc961 NC |
340 | (The Windows -C command flag "wide API support" has been at least |
341 | temporarily retired in 5.8.1, and the -C has been repurposed, see | |
342 | L<perlrun>.) | |
969e704b | 343 | |
0bdfc961 | 344 | =head2 Unicode in %ENV |
969e704b | 345 | |
0bdfc961 | 346 | Currently the %ENV entries are always byte strings. |
e50bb9a1 | 347 | |
0bdfc961 | 348 | =head2 use less 'memory' |
e50bb9a1 | 349 | |
0bdfc961 NC |
350 | Investigate trade offs to switch out perl's choices on memory usage. |
351 | Particularly perl should be able to give memory back. | |
e50bb9a1 | 352 | |
0bdfc961 | 353 | This task is incremental - even a little bit of work on it will help. |
0abe3f7c | 354 | |
0bdfc961 | 355 | =head2 Re-implement C<:unique> in a way that is actually thread-safe |
0abe3f7c | 356 | |
0bdfc961 NC |
357 | The old implementation made bad assumptions on several levels. A good 90% |
358 | solution might be just to make C<:unique> work to share the string buffer | |
359 | of SvPVs. That way large constant strings can be shared between ithreads, | |
360 | such as the configuration information in F<Config>. | |
0abe3f7c | 361 | |
0bdfc961 | 362 | =head2 Make tainting consistent |
0abe3f7c | 363 | |
0bdfc961 NC |
364 | Tainting would be easier to use if it didn't take documented shortcuts and |
365 | allow taint to "leak" everywhere within an expression. | |
0abe3f7c | 366 | |
0bdfc961 | 367 | =head2 readpipe(LIST) |
0abe3f7c | 368 | |
0bdfc961 NC |
369 | system() accepts a LIST syntax (and a PROGRAM LIST syntax) to avoid |
370 | running a shell. readpipe() (the function behind qx//) could be similarly | |
371 | extended. | |
0abe3f7c | 372 | |
e50bb9a1 | 373 | |
e50bb9a1 | 374 | |
e50bb9a1 | 375 | |
f86a8bc5 | 376 | |
0bdfc961 | 377 | =head1 Tasks that need a knowledge of the interpreter |
3298bd4d | 378 | |
0bdfc961 NC |
379 | These tasks would need C knowledge, and knowledge of how the interpreter works, |
380 | or a willingness to learn. | |
3298bd4d | 381 | |
0bdfc961 NC |
382 | =head2 lexical pragmas |
383 | ||
384 | Reimplement the mechanism of lexical pragmas to be more extensible. Fix | |
385 | current pragmas that don't work well (or at all) with lexical scopes or in | |
386 | run-time eval(STRING) (C<sort>, C<re>, C<encoding> for example). MJD has a | |
387 | preliminary patch that implements this. | |
0562c0e3 | 388 | |
d10fc472 | 389 | =head2 Attach/detach debugger from running program |
1626a787 | 390 | |
cd793d32 NC |
391 | The old perltodo notes "With C<gdb>, you can attach the debugger to a running |
392 | program if you pass the process ID. It would be good to do this with the Perl | |
0bdfc961 NC |
393 | debugger on a running Perl program, although I'm not sure how it would be |
394 | done." ssh and screen do this with named pipes in /tmp. Maybe we can too. | |
1626a787 | 395 | |
0bdfc961 | 396 | =head2 inlining autoloaded constants |
d10fc472 | 397 | |
0bdfc961 NC |
398 | Currently the optimiser can inline constants when expressed as subroutines |
399 | with prototype ($) that return a constant. Likewise, many packages wrapping | |
400 | C libraries export lots of constants as subroutines which are AUTOLOADed on | |
401 | demand. However, these have no prototypes, so can't be seen as constants by | |
402 | the optimiser. Some way of cheaply (low syntax, low memory overhead) to the | |
403 | perl compiler that a name is a constant would be great, so that it knows to | |
404 | call the AUTOLOAD routine at compile time, and then inline the constant. | |
80b46460 | 405 | |
0bdfc961 | 406 | =head2 Constant folding |
80b46460 | 407 | |
0bdfc961 NC |
408 | The peephole optimiser should trap errors during constant folding, and give |
409 | up on the folding, rather than bailing out at compile time. It is quite | |
410 | possible that the unfoldable constant is in unreachable code, eg something | |
411 | akin to C<$a = 0/0 if 0;> | |
412 | ||
413 | =head2 LVALUE functions for lists | |
414 | ||
415 | The old perltodo notes that lvalue functions don't work for list or hash | |
416 | slices. This would be good to fix. | |
417 | ||
418 | =head2 LVALUE functions in the debugger | |
419 | ||
420 | The old perltodo notes that lvalue functions don't work in the debugger. This | |
421 | would be good to fix. | |
422 | ||
423 | =head2 _ prototype character | |
424 | ||
425 | Study the possibility of adding a new prototype character, C<_>, meaning | |
426 | "this argument defaults to $_". | |
427 | ||
428 | =head2 @INC source filter to Filter::Simple | |
429 | ||
430 | The second return value from a sub in @INC can be a source filter. This isn't | |
431 | documented. It should be changed to use Filter::Simple, tested and documented. | |
432 | ||
433 | =head2 regexp optimiser optional | |
434 | ||
435 | The regexp optimiser is not optional. It should configurable to be, to allow | |
436 | its performance to be measured, and its bugs to be easily demonstrated. | |
437 | ||
438 | =head2 UNITCHECK | |
439 | ||
440 | Introduce a new special block, UNITCHECK, which is run at the end of a | |
441 | compilation unit (module, file, eval(STRING) block). This will correspond to | |
442 | the Perl 6 CHECK. Perl 5's CHECK cannot be changed or removed because the | |
443 | O.pm/B.pm backend framework depends on it. | |
444 | ||
445 | =head2 optional optimizer | |
446 | ||
447 | Make the peephole optimizer optional. Currently it performs two tasks as | |
448 | it walks the optree - genuine peephole optimisations, and necessary fixups of | |
449 | ops. It would be good to find an efficient way to switch out the | |
450 | optimisations whilst keeping the fixups. | |
451 | ||
452 | =head2 You WANT *how* many | |
453 | ||
454 | Currently contexts are void, scalar and list. split has a special mechanism in | |
455 | place to pass in the number of return values wanted. It would be useful to | |
456 | have a general mechanism for this, backwards compatible and little speed hit. | |
457 | This would allow proposals such as short circuiting sort to be implemented | |
458 | as a module on CPAN. | |
459 | ||
460 | =head2 lexical aliases | |
461 | ||
462 | Allow lexical aliases (maybe via the syntax C<my \$alias = \$foo>. | |
463 | ||
464 | =head2 entersub XS vs Perl | |
465 | ||
466 | At the moment pp_entersub is huge, and has code to deal with entering both | |
467 | perl and XS subroutines. Subroutine implementations rarely change between | |
468 | perl and XS at run time, so investigate using 2 ops to enter subs (one for | |
469 | XS, one for perl) and swap between if a sub is redefined. | |
2810d901 NC |
470 | |
471 | =head2 Self ties | |
472 | ||
473 | self ties are currently illegal because they caused too many segfaults. Maybe | |
474 | the causes of these could be tracked down and self-ties on all types re- | |
475 | instated. | |
0bdfc961 NC |
476 | |
477 | =head2 Optimize away @_ | |
478 | ||
479 | The old perltodo notes "Look at the "reification" code in C<av.c>". | |
480 | ||
481 | =head2 switch ops | |
482 | ||
483 | The old perltodo notes "Although we have C<Switch.pm> in core, Larry points to | |
484 | the dormant C<nswitch> and C<cswitch> ops in F<pp.c>; using these opcodes would | |
485 | be much faster." | |
486 | ||
487 | =head2 What hooks would assertions need? | |
488 | ||
489 | Assertions are in the core, and work. However, assertions needed to be added | |
490 | as a core patch, rather than an XS module in ext, or a CPAN module, because | |
491 | the core has no hooks in the necessary places. It would be useful to | |
492 | investigate what hooks would need to be added to make it possible to provide | |
493 | the full assertion support from a CPAN module, so that we aren't constraining | |
494 | the imagination of future CPAN authors. | |
495 | ||
496 | ||
497 | ||
498 | ||
499 | ||
500 | ||
501 | ||
502 | =head1 Big projects | |
503 | ||
504 | Tasks that will get your name mentioned in the description of the "Highlights | |
505 | of 5.10" | |
506 | ||
507 | =head2 make ithreads more robust | |
508 | ||
509 | Generally make ithreads more robust. See also L<iCOW> | |
510 | ||
511 | This task is incremental - even a little bit of work on it will help, and | |
512 | will be greatly appreciated. | |
513 | ||
514 | =head2 iCOW | |
515 | ||
516 | Sarathy and Arthur have a proposal for an improved Copy On Write which | |
517 | specifically will be able to COW new ithreads. If this can be implemented | |
518 | it would be a good thing. | |
519 | ||
520 | =head2 (?{...}) closures in regexps | |
521 | ||
522 | Fix (or rewrite) the implementation of the C</(?{...})/> closures. | |
523 | ||
524 | =head2 A re-entrant regexp engine | |
525 | ||
526 | This will allow the use of a regex from inside (?{ }), (??{ }) and | |
527 | (?(?{ })|) constructs. |