Author: particle
Date: 2009-01-09 22:17:42 +0100 (Fri, 09 Jan 2009)
New Revision: 24848

Modified:
   docs/Perl6/Spec/S19-commandline.pod
Log:
[S19] a note on assumptions

Modified: docs/Perl6/Spec/S19-commandline.pod
===================================================================
--- docs/Perl6/Spec/S19-commandline.pod 2009-01-09 21:13:19 UTC (rev 24847)
+++ docs/Perl6/Spec/S19-commandline.pod 2009-01-09 21:17:42 UTC (rev 24848)
@@ -15,7 +15,7 @@
   Maintainer: Jerry Gay <jerry....@rakudoconsulting.com>
   Date: 12 Dec 2008
   Last Modified: 9 Jan 2009
-  Version: 14
+  Version: 15
 
 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
@@ -51,14 +51,14 @@
 
 This interface to Perl 6 is special in that it occurs at the intersection of
 the program and the operating system's command line shell, and thus is not
-accessed via a consistent syntax everywhere. Perl is born of Unix, and as such
-the syntax presented in this document is expected to work in a Unix-style
-shell. To explore the particularities of other operating systems, see
-L<Synopsis 25|S25-portability> (TBD).
+accessed via a consistent syntax everywhere. A few assumptions are made here,
+which will hopefully stand the test of time: All command-line arguments are
+assumed to be in Unicode unless proven otherwise; and Perl is born of Unix,
+and as such the syntax presented in this document is expected to work in a
+Unix-style shell. To explore the particularities of other operating systems,
+see L<Synopsis 25|S25-portability> (TBD).
 
 
-[my notes/conjectures below are all in square brackets  --TimToady]
-
 =head1 Command Line Elements
 
 The command line is broken down into two basic elements: a I<program>, and
@@ -574,15 +574,6 @@
 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?
-
-[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
-of marking arguments as needing to be encoded into a Buf.  but for sanity
-we must try to settle on unicode as the default expectation.  I hope POSIX
-dies before Perl 6 does...]
-
 Sandboxing? maybe-r
 
 Env var? maybe -E.

Reply via email to