Skip to content

Commit

Permalink
[S19] a note on assumptions
Browse files Browse the repository at this point in the history
git-svn-id: http://svn.pugscode.org/pugs@24848 c213334d-75ef-0310-aa23-eaa082d1ae64
  • Loading branch information
particle committed Jan 9, 2009
1 parent 5a777b1 commit 2d0eb64
Showing 1 changed file with 7 additions and 16 deletions.
23 changes: 7 additions & 16 deletions S19-commandline.pod
Expand Up @@ -15,7 +15,7 @@ Jerry Gay <jerry.gay@rakudoconsulting.com>
Maintainer: Jerry Gay <jerry.gay@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
Expand Down Expand Up @@ -51,14 +51,14 @@ New C<++> metasyntax allows options to be passed through to subsystems

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
Expand Down Expand Up @@ -574,15 +574,6 @@ 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.

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.
Expand Down

0 comments on commit 2d0eb64

Please sign in to comment.