summaryrefslogtreecommitdiff
path: root/pod/perltodo.pod
diff options
context:
space:
mode:
authorJarkko Hietaniemi <jhi@iki.fi>2001-08-12 18:45:52 +0000
committerJarkko Hietaniemi <jhi@iki.fi>2001-08-12 18:45:52 +0000
commit4b3b956a126d728a1e0e01e3e39db2489fd761a8 (patch)
tree827ac8d868dbfd00e870af7d7ff9c443097f2648 /pod/perltodo.pod
parent4c53e876b789c79a3c29f9f39f439b5326c8d417 (diff)
downloadperl-4b3b956a126d728a1e0e01e3e39db2489fd761a8.tar.gz
Todo updates and fixes.
p4raw-id: //depot/perl@11649
Diffstat (limited to 'pod/perltodo.pod')
-rw-r--r--pod/perltodo.pod26
1 files changed, 9 insertions, 17 deletions
diff --git a/pod/perltodo.pod b/pod/perltodo.pod
index 3c7243254e..f409b1ea22 100644
--- a/pod/perltodo.pod
+++ b/pod/perltodo.pod
@@ -20,13 +20,16 @@ of archives may be found at:
C<perlio> provides this, but the interface could be a lot more
straightforward.
-=head2 Eliminate need for "use utf8";
+=head2 Autoload bytes.pm
-While the C<utf8> pragma is autoloaded when necessary, it's still needed
-for things like Unicode characters in a source file. The UTF8 hint can
-always be set to true, but it needs to be set to false when F<utf8.pm>
-is being compiled. (To stop Perl trying to autoload the C<utf8>
-pragma...)
+When the lexer sees, for instance, C<bytes::length>, it should
+automatically load the C<bytes> pragma.
+
+=head2 Make "\u{XXXX}" et al work
+
+Danger, Will Robinson! Discussing the semantics of C<"\x{F00}">,
+C<"\xF00"> and C<"\U{F00}"> on P5P I<will> lead to a long and boring
+flamewar.
=head2 Create a char *sv_pvprintify(sv, STRLEN *lenp, UV flags)
@@ -51,17 +54,6 @@ Possible options, controlled by the flags:
- append a "..." to the produced string if the maximum length is exceeded
- really fancy: print unicode characters as \N{...}
-=head2 Autoload byte.pm
-
-When the lexer sees, for instance, C<bytes::length>, it should
-automatically load the C<bytes> pragma.
-
-=head2 Make "\u{XXXX}" et al work
-
-Danger, Will Robinson! Discussing the semantics of C<"\x{F00}">,
-C<"\xF00"> and C<"\U{F00}"> on P5P I<will> lead to a long and boring
-flamewar.
-
=head2 Overloadable regex assertions
This may or may not be possible with the current regular expression