From: Jarkko Hietaniemi Date: Tue, 14 Aug 2001 13:44:40 +0000 (+0000) Subject: Todo updates. X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=f86a8bc58a487e28b31c5d91c65920f4859f3f74;p=p5sagit%2Fp5-mst-13.2.git Todo updates. p4raw-id: //depot/perl@11671 --- diff --git a/pod/perltodo.pod b/pod/perltodo.pod index f409b1e..c6d64bd 100644 --- a/pod/perltodo.pod +++ b/pod/perltodo.pod @@ -283,6 +283,12 @@ is the bootstrapping build process of Perl: if the filesystem the target systems sees is not the same what the build host sees, various input, output, and (Perl) library files need to be copied back and forth. +As of 5.8.0 Configure mostly works for cross-compilation +(used successfully for iPAQ Linux), miniperl gets built, +but then building DynaLoader (and other extensions) fails +since MakeMaker knows nothing of cross-compilation. +(See INSTALL/Cross-compilation for the state of things.) + =head2 Perl preprocessor / macros Source filters help with this, but do not get us all the way. For @@ -491,7 +497,7 @@ Ideas which have been discussed, and which may or may not happen. It's unclear what this should do or how to do it without breaking old code. -=head2 Make tr/// return histogram +=head2 Make tr/// return histogram of characters in list context There is a patch for this, but it may require Unicodification. @@ -780,6 +786,7 @@ Suggesting this on P5P B cause a boring and interminable flamewar. =head2 "class"-based lexicals Use flyweight objects, secure hashes or, dare I say it, pseudo-hashes instead. +(Or whatever will replace pseudohashes in 5.10.) =head2 byteperl @@ -787,18 +794,19 @@ C covers this. =head2 Lazy evaluation / tail recursion removal -C in core gives some of these; tail recursion removal is -done manually, with C. (However, MJD has found that -C introduces a performance penalty, so maybe there should -be a way to do this after all: C is -better.) +C gives first() (a short-circuiting grep); tail recursion +removal is done manually, with C. (However, MJD has +found that C introduces a performance penalty, so maybe +there should be a way to do this after all: C is better.) =head2 Make "use utf8" the default -There is a patch available for this, search p5p archives for -the Subject "[EXPERIMENTAL PATCH] make unicode (utf8) default" -but this would be unacceptable because of backward compatibility: -scripts could not contain B. Also would -introduce a measurable slowdown of at least few percentages since all -regular expression operations would be done in full UTF-8. +Because of backward compatibility this is difficult: scripts could not +contain B (like Latin-1) anymore, even in +string literals or pod. Also would introduce a measurable slowdown of +at least few percentages since all regular expression operations would +be done in full UTF-8. But if you want to try this, add +-DUSE_UTF8_SCRIPTS to your compilation flags. +