X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=pod%2Fperltodo.pod;h=1898b118d40ad4912e18828766bbe42b4d93eff2;hb=17c338f39c13131c1bc175ef38013b54bc98396d;hp=1f57c0c1eacd42e8b9c78257e756140afb9233ac;hpb=f34dec15bb9e49ae0039c78141053106a14a4caf;p=p5sagit%2Fp5-mst-13.2.git

diff --git a/pod/perltodo.pod b/pod/perltodo.pod
index 1f57c0c..1898b11 100644
--- a/pod/perltodo.pod
+++ b/pod/perltodo.pod
@@ -73,19 +73,12 @@ C<\p{IsPs}>.
 
 =item *
 
-Allow for the metaproperties C<Any> and C<Assigned>, and C<Common>;
-C<Alphabetic>, C<Ideographic>, C<Lowercase>, C<Uppercase> (note that
-are large classes than the general categories C<Lu> and C<Ll>),
-C<White Space>, C<Bidi Control>, C<Join Control>, C<ASCII Hex Digit>,
-C<Hex Digit>, <Noncharacter Code Point>, C<ID Start>, C<ID Continue>,
-C<XID Start>, C<XID Continue>, C<NF*_NO>, C<NF*_MAYBE>.
-
-There are also enumerated properties: C<Decomposition Type>,
-C<Numeric Type>, C<East Asian Width>, C<Line Break>.  These
-properties have multiple values: for uniqueness the property
-value should be appended.  For example, C<\p{IsAlphabetic}>
-wouldbe the binary property, while C<\p{AlphabeticLineBreak}>
-would mean the enumerated property.
+Allow for the metaproperties: C<XID Start>, C<XID Continue>,
+C<NF*_NO>, C<NF*_MAYBE> (require the DerivedCoreProperties and
+DerviceNormalizationProperties files).
+
+There are also multiple value properties still unimplemented:
+C<Numeric Type>, C<East Asian Width>.
 
 =item *
 
@@ -196,11 +189,6 @@ Have a way to introduce user-defined opcodes without the subroutine call
 overhead of an XSUB; the user should be able to create PP code. Simon
 Cozens has some ideas on this.
 
-=head2 spawnvp() on Win32
-
-Win32 has problems spawning processes, particularly when the arguments
-to the child process contain spaces, quotes or tab characters.
-
 =head2 DLL Versioning
 
 Windows needs a way to know what version of a XS or C<libperl> DLL it's
@@ -305,7 +293,7 @@ That's to say, C<pack "(sI)40"> would be the same as C<pack "sI"x40>
 =head2 Cross compilation
 
 Make Perl buildable with a cross-compiler. This will play havoc with
-Configure, which needs to how how the target system will respond to
+Configure, which needs to know how the target system will respond to
 its tests; maybe C<microperl> will be a good starting point here.
 (Indeed, Bart Schuller reports that he compiled up C<microperl> for
 the Agenda PDA and it works fine.)  A really big spanner in the works