Add newSVuv().

[p5sagit/p5-mst-13.2.git] / Todo-5.6

diff --git a/Todo-5.6 b/Todo-5.6
index b9f05fd..35e6949 100644 (file)
--- a/Todo-5.6
+++ b/Todo-5.6
@@ -43,13 +43,23 @@ Namespace cleanup
     API-space:    complete the list of things that constitute public api
 
 Configure
+    fix the vicious cyclic multidependency of cc <-> libpth <-> loclibpth
+       libswanted <-> usethreads <-> use64bitint <-> use64bitall <->
+       uselargefiles <-> ...  
     make configuring+building away from source directory work (VPATH et al)
-    _r support
-    cross-compilation configuring
+       this is related to: cross-compilation configuring
+       host vs target: compile in the host, get the executable to the target,
+       get the possible input files to the target, execute in the target,
+       get possible output files back to to host.  this needs to work
+       both during Configure and during the build.  You cannot assume
+       shared filesystems between the host and the target, executing
+       the target executable may involve e.g. rsh
+    _r support (see Todo for mode detailed description)
     POSIX 1003.1 1996 Edition support--realtime stuff:
        POSIX semaphores, message queues, shared memory, realtime clocks,
        timers, signals (the metaconfig units mostly already exist for these)
     UNIX98 support: reader-writer locks, realtime/asynchronous IO
+    IPv6 support: see RFC2292, RFC2553
 
 Long doubles
     figure out where the PV->NV->PV conversion gets it wrong at least
@@ -82,6 +92,18 @@ Locales
 
 Regexen
    make RE engine thread-safe
+   a way to do full character set arithmetics: now one can do
+       addition, negate a whole class, and negate certain subclasses
+       (e.g. \D, [:^digit:]), but a more generic way to add/subtract/
+       intersect characters/classes, like described in the Unicode technical
+       report on Regular Expression Guidelines,
+       http://www.unicode.org/unicode/reports/tr18/
+       (amusingly, the TR notes that difference and intersection
+        can be done using "Perl-style look-ahead")
+       difference syntax?  maybe [[:alpha:][^abc]] meaning
+       "all alphabetic expect a, b, and c"? or [[:alpha:]-[abc]]?
+       (maybe bad, as we explicitly disallow such 'ranges')
+       intersection syntax? maybe [[..]&[...]]?
    POSIX [=bar=] and [.zap.] would nice too but there's no API for them
        =bar= could be done with Unicode, though, see the Unicode TR #15 about
        normalization forms: