Author: particle
Date: 2009-01-09 03:20:40 +0100 (Fri, 09 Jan 2009)
New Revision: 24823
Modified:
docs/Perl6/Spec/S19-commandline.pod
Log:
[S19] incorporate more of TimToady++'s notes, and format Notes section as
proper Pod
Modified: docs/Perl6/Spec/S19-commandline.pod
===================================================================
--- docs/Perl6/Spec/S19-commandline.pod 2009-01-09 02:07:28 UTC (rev 24822)
+++ docs/Perl6/Spec/S19-commandline.pod 2009-01-09 02:20:40 UTC (rev 24823)
@@ -15,7 +15,7 @@
Maintainer: Jerry Gay <jerry....@rakudoconsulting.com>
Date: 12 Dec 2008
Last Modified: 8 Jan 2009
- Version: 12
+ Version: 13
This is a draft document. This document describes the command line interface.
It has changed extensively from previous versions of Perl in order to increase
@@ -510,13 +510,12 @@
=item PERL6LIB
-A list of directories in which to look for Perl library files.
+A list of directories in which to look for ad hoc Perl library files.
-Note: this is speculative, as library loading is not yet specified.
+Note: this is speculative, as library loading is not yet specified,
+except insofar as S11 mandates various behaviors incompatible with
+mere directory probing.
-[except insofar as S11 mandates various behaviors incompatible with
-mere directory probing...]
-
=item PERL6OPT
Default command-line arguments. Arguments found here are prepended to the
@@ -548,16 +547,14 @@
=head1 Notes
-{{ -jg
-i'd like to be able to adjust the input record separator from command line,
-for instance to specify the equivalent of perl 5's C<$/ = \32768;>. so far,
-i don't have a solution, but perhaps pass a closure that evaluates to an int?
+I'd like to be able to adjust the input record separator from command line,
+for instance to specify the equivalent of perl 5's C<$/ = \32768;>. So far,
+I don't have a solution, but perhaps pass a closure that evaluates to an Int?
+This should try to use whatever option does the same thing to a new
+filehandle when S16 is further developed.
-[this should try to use whatever option does the same thing to a new
-filehandle when S16 is further developed.]
+Do I need to address any unicode concerns?
-do i need to address any unicode concerns?
-
[You can try "all command line arguments are assumed to be in unicode
unless proven otherwise" and see how well it flies. :) but this starts
to get into filenames-are-blobs kind of issues...maybe we need a way
@@ -565,16 +562,9 @@
we must try to settle on unicode as the default expectation. I hope POSIX
dies before Perl 6 does...]
-loading a switch parsing module by a switch, instead of using the default.
-maybe via ++RTS, since it needs to happen *before* switches are evaluated.
+Sandboxing? maybe-r
-[suggest ++CMD --use_cmd_module ++/CMD]
+Env var? maybe -E.
+Could be posed in terms of substituting a different prelude.
-sandboxing? maybe-r
-
-env var? maybe -E
-
-[could be posed in terms of substituting a different prelude]
-}}
-
=for vim:set expandtab sw=4:
