From: Artur Bergman Date: Sun, 12 May 2002 19:10:27 +0000 (+0000) Subject: Update todo, removing things done and adding new things. X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=56490ca27afa917d6cb7870ae8b8cd495d4225dd;hp=c133c03fba8fc439e535e387ad9f4605abbe0e8c;p=p5sagit%2Fp5-mst-13.2.git Update todo, removing things done and adding new things. p4raw-id: //depot/perl@16562 --- diff --git a/pod/perltodo.pod b/pod/perltodo.pod index 0a6b8e1..0079cd7 100644 --- a/pod/perltodo.pod +++ b/pod/perltodo.pod @@ -112,17 +112,18 @@ class subtraction. http://www.unicode.org/unicode/reports/tr18/ -=head2 use Thread for iThreads +=head2 Work out exit/die semantics for threads -Artur Bergman's C module is a start on this, but needs to -be more mature. +There are some suggestion for use a +C x> syntax. -=head2 make perl_clone optionally clone ops +http://archive.develooper.com/perl5-porters@perl.org/msg79618.html -So that pseudoforking, mod_perl, iThreads and nvi will work properly -(but not as efficiently) until the regex engine is fixed to be threadsafe. +=head2 Better support for nonpreemptive threading systems like PTH -=head2 Work out exit/die semantics for threads +Perhaps do yield() before blocking calls, exchange calls to non blocking +calls specific for those libraries (for example GNUpth has a pth_sleep +which is a non pth aware version of sleep). =head2 Typed lexicals for compiler @@ -170,10 +171,6 @@ One possible solution would be to adopt/support ICU: http://oss.software.ibm.com/developerworks/opensource/icu/project/ -=head2 Thread-safe regexes - -The regular expression engine is currently non-threadsafe. - =head2 Arithmetic on non-Arabic numerals C<[1234567890]> aren't the only numerals any more.