From 94da6c299b439da84cecd761520b3ad01ef3a7ac Mon Sep 17 00:00:00 2001 From: Jarkko Hietaniemi Date: Tue, 12 Jun 2007 06:15:26 +0300 Subject: [PATCH] perltodo: more vtable musings Message-Id: <200706120015.l5C0FQH7512295@kosh.hut.fi> p4raw-id: //depot/perl@31367 --- pod/perltodo.pod | 22 ++++++++++++++-------- 1 file changed, 14 insertions(+), 8 deletions(-) diff --git a/pod/perltodo.pod b/pod/perltodo.pod index 6a0d33d..925c157 100644 --- a/pod/perltodo.pod +++ b/pod/perltodo.pod @@ -511,6 +511,8 @@ PerlIO doesn't do directories or symlinks, either: mkdir(), rmdir(), opendir(), closedir(), seekdir(), rewinddir(), glob(); symlink(), readlink(). +See also L. + =head2 -C on the #! line It should be possible to make -C work correctly if found on the #! line, @@ -643,14 +645,18 @@ probably does not need to survive alongside this proposed new implementation, the approaches could be merged. What would this give us? One often-asked-for feature this would -enable is using Unicode for filenames (and other "names" like %ENV, -usernames, hostnames, and so forth.) But this would also allow for -things like virtual filesystems, virtual networks, and "sandboxes" -(though as long as dynamic loading of random object code is allowed, -not very safe sandboxes since external code of course know not of -Perl's vtables). An example of a smaller "sandbox" is that this -feature can be used to implement per-thread working directories: -Win32 already does this. +enable is using Unicode for filenames, and other "names" like %ENV, +usernames, hostnames, and so forth. +(See L.) + +But this kind of virtualization would also allow for things like +virtual filesystems, virtual networks, and "sandboxes" (though as long +as dynamic loading of random object code is allowed, not very safe +sandboxes since external code of course know not of Perl's vtables). +An example of a smaller "sandbox" is that this feature can be used to +implement per-thread working directories: Win32 already does this. + +See also L. =head1 Big projects -- 2.7.4