DRAFT: Synopsis 19: Command Line Interface
Created: 12 Dec 2008
Last Modified: 06 Oct 2014
Version: 28
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 clarity, consistency, and extensibility. Many of the syntax revisions are extensions, so you'll find that much of the Perl 5 syntax embedded in your muscle memory will still work.
Notable features described in the sections below include:
++ 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. 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 Synopsis 25 (TBD).
The command line is broken down into two basic elements: a program, and arguments. Each command line element is whitespace separated, so elements containing whitespace must be quoted. The program processes the arguments and performs the requested actions. It looks something like /usr/bin/perl6, parrot perl6.pbc, or rakudo (or mono niecza.exe, et cetera), and is followed by zero or more arguments. The program portion of the command line is made available at run-time via the PROCESS::<$PROGRAM> variable (normally accessed as $*PROGRAM) as an IO::Path.
Command line arguments are broken down into options and values. Each option may take zero or more values. After all options have been processed, the remaining values (if any) generally consist of the name of a script for Perl to execute, followed by arguments for that script. If no values remain, Perl 6 implicitly opens STDIN to read the script. If you wish to pass arguments to a script read from STDIN, you must specify STDIN by name (- on most operating systems).
You may find yourself typing your favorite Perl 5 options, even after Christmas has arrived. As you'll see below, common options are provided which behave similarly. Less common options, however, may not be available or may have changed syntax. If you provide Perl with unrecognized command-line syntax, Perl gives you a friendly error message. If the unrecognized syntax is a valid Perl 5 option, Perl provides helpful suggestions to allow you to perform the same action using the current syntax.
Several features have not changed from Perl 5, including:
Option... Still means...
-a Autosplit
-c Check syntax
-e *line* Execute
-F *expression* Specify autosplit field separator
-h Display help and exit
-I *directory*[,*directory*[,...]] Unshift CompUnitRepo::Local('s) to @?INC
-n Act like awk
-p Act like sed
-S Search PATH for script
-T Enable taint mode
-v Display version info
-V Display verbose config info
All of these options have extended syntax, and some may have slightly different semantics, so see "Option Reference" below for the details.
Some Perl 5 command-line features are no longer available, either because there's a new and different way to do it in Perl 6, or because they're no longer relevant. Here's a breakdown of what's been removed:
Sets input record separator. Missing due to lack of specification in Synopsis 16. There is a comment about this in the "Notes" section at the end of this document.
Control unicode features. Perl 6 has unicode semantics, and assumes a UTF-8 command-line interface (until proven otherwise, at which point this functionality may be readdressed).
Debugging commands. Replaced with the ++BUG metasyntactic option.
Execute a line of code, with all features enabled. This is specific to Perl 5.10, and not relevant to Perl 6, where -e performs this function.
Modify files in-place. Haven't thought about it enough to add yet, but I'm certain it has a strong following. {{TODO review decision here}}
Enable automatic line-ending processing. This is the default behavior.
use/no module. Replaced by --use.
Run option through C preprocessor. This caused problems for Perl 5, and is completely obsolete now.
Enable rudimentary switch parsing. By default, Perl 6 parses the arguments passed to a script using the signature supplied by the user in the MAIN routine (see "Declaring a MAIN subroutine" in S06).
Enable taint warnings mode. Taint mode needs more thought, but it's much more likely that the -T switch will take options rather than use a second command-line flag to implement related behavior.
Dump the core after parsing the program. This has been deemed obsolete.
Allow unsafe operations. This is extremely dangerous and infrequently used, and doesn't deserve its own command-line option.
Enable warnings. This is the default behavior.
Enable all warnings. This is infrequently used, and doesn't deserve its own command-line option.
Disable all warnings. This is infrequently used, and doesn't deserve its own command-line option.
Command line options are parsed using the following rules:
--, -, or :.
-o and -O are not the same option.
-- or :.
-.
-ab means -a -b. When a single-character option which requires a value is clustered, the option may appear only in the final position of the cluster.
/, for example --/name, :/name, -/n. Negated single-character options cannot appear in a cluster. In practice, negated options are rare anyway, as most boolean options default to False.
' is not allowed, and single-character options may be any character or number.
-- and -e <program> signal the parser to stop option processing. Arguments following a bare -- (with no identifier) or a -e are always parsed as a list of values, even if they look like valid options.
Delimited options allow you to transparently pass one or more options through to a subsystem, as specified by the special options that delimit those options. They are parsed according to the following rules:
++. You'll usually use two plus characters, but more are allowed to avoid ambiguity when nesting delimited options.
-- option does not suppress searching for the closing delimiter. That is, only the rest of the arguments within the delimiters are treated as values.
These options are made available in dynamic variables matching their name, and are invisible to MAIN() except as %*OPTS<name>. For example:
++PARSER --setting=Perl6-autoloop-no-print ++/PARSER
is available inside your script as %*OPTS<PARSER>, and contains --setting=Perl6-autoloop-no-print. Since eager matching is used, if you need to pass something like:
++foo -bar ++foo baz ++/foo ++/foo
you'll end up with
%*OPTS<foo> = '-bar ++foo baz';
which is probably not what you wanted. Instead, add extra + characters
+++foo -bar ++foo baz ++/foo +++/foo
which will give you
%*OPTS<foo> = '-bar ++foo baz ++/foo';
allowing you to properly nest delimited options.
The actual storage location of %*OPTS may be either in PROCESS::<%OPTS> or GLOBAL::<%OPTS>, depending on how the process sets up its interpreters.
Values are parsed with the following rules:
--option=value or --option value.
-O="spacey value"
--option=val1 --option='val 2'.
Any remaining arguments to the Perl6 program are placed in the @*ARGS array.
Perl 6 options, descriptions, and services.
multi sub perl6(
Bool :a($autoloop-comb),
Bool :c($check-syntax),
Bool :$doc,
:e($execute),
:F($autoloop-delim),
Bool :h($help),
:I(@include),
:L($language),
Bool :n($autoloop-no-print),
:O($output-format),
Bool :p($autoloop-print),
Bool :S($search-path),
Bool :T($taint),
:u($use),
Bool :v($version),
Bool :V($verbose-config),
Bool :x($extract-from-text),
);
When used with -n or -p, implicitly combs input and assigns the result to @_ within the loop produced by the -n or -p.
The default pattern is /\S+/, an alternate pattern for comb may be specified with --autoloop-pattern, a.k.a. -F.
Add a command-line processor. When this option is parsed, it immediately triggers an action that affects or replaces the command-line parser. Therefore, it is a good idea to put this option as early as possible in the argument list.
Check syntax, then exit. Desugars to -e 'CHECK { compiles_ok(); exit; }'.
Lookup Perl documentation in Pod format. Desugars to -e 'CHECK { compiles_ok(); dump_perldoc(); }'. $*ARGS contains the arguments passed to perl6, and is available at CHECK time, so dump_perldoc() can respond to command-line options.
{{TODO may create a ++DOC subsystem here. also, may use -d for short name, even though it clashes with perl 5}}
Set switches and flags for the debugger.
Note: The debugger needs further specification.
Execute a single-line program in lax mode.
If you don't wish to run in lax mode, but with strictures and warnings enabled, pass 'use strict;' at the -e on the command line, like -e 'use strict; my $x = 42'.
Pattern to split on (used with -a). Substitutes an expression for the default split function, which is {split ' '}. Accepts unicode strings (as long as your shell lets you pass them). Allows passing a closure (e.g. -F "{use Text::CSV}"). Awk's not better any more :)
Print summary of options. Desugars to ++CMD --print-help --exit ++/CMD.
Prepend CompUnitRepo's to @?INC, for ad hoc module searching. The CompUnitRepo::Local::File class will be assumed if no class has been specified. Any class specified should adhere to the CompUnitRepo interface. In any Searching the standard library follows the policies laid out in Synopsis 11.
Set the domain specific language for parsing the script file. (That is, specify the setting (often known as the prelude) for the program.) ++PARSER --setting=*dsl* ++/PARSER.
Act like awk. Desugars to ++PARSER --setting=Perl6-autoloop-no-print ++/PARSER.
Emit compiler output to STDOUT in the specified format, rather than invoking the compiled code immediately. This option is implementation-specific, so consult the documentation for your Perl 6 implementation for further details.
Act like sed. Desugars to ++PARSER --setting=Perl6-autoloop-print ++/PARSER.
Use PATH environment variable to search for script specified on command-line.
Turns on "taint" checking. See Synopsis 23 for details. Commits very early. Put this option as early on the command-line as possible.
--use *module* and -u *module* desugars to -e 'use *module*'. Specify version info and import symbols by appending info to the module name:
-u'Sense:auth<cpan:JRANDOM>:ver<1.2.1> <common @horse>'
You'll need the quotes so your shell doesn't complain about redirection. There is no special command-line syntax for 'no *module*, use -e.
Display program name, version, patchlevel, etc. Desugars to ++CMD -v ++/CMD ++PARSER -v ++/PARSER ++BUG -v ++/BUG.
Display configuration details. Desugars to ++CMD -V ++/CMD ++PARSER -V ++/PARSER ++BUG -V ++/BUG.
Run program embedded in Unicode text. Scan for the first line starting with #! and containing the word perl, and start there instead. This is useful for running a program embedded in a larger message. (In this case you would indicate the end of the program using the =END block, as defined in Synopsis 26.)
Desugars to --PARSER --Perl6-extract-from-text --/PARSER.
Metasyntactic options are a subset of delimited options used to pass arguments to an underlying component of Perl. Perl itself does not parse these options, but makes them available to run-time components via the %*META-ARGS dynamic variable.
Standard in Perl 6 are three underlying components, CMD, PARSER, and BUG. Implementations may expose other components via this interface, so consult the documentation for your Perl 6 implementation.
On command line... Subsystem gets... ++X a -b ++/X a -b
# Nested options +++X a -b ++X -c ++/X -d e +++/X a -b ++X -c ++/X -d e
# More than once (both are valid, but the second form is preferred) ++X a -b ++/X -c ++X -d e ++/X a -b -d e +++X a -b +++/X -c ++X -d e ++/X a -b -d e
Environment variables may be used to the same effect as command-line arguments.
Used in executing subprocesses, and for finding the program if the -S switch is used.
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, except insofar as S11 mandates various behaviors incompatible with mere directory probing.
Default command-line arguments. Arguments found here are prepended to the list of arguments provided on the command-line.
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 $/ = \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.
Jerry Gay <jerry.gay@rakudoconsulting.com>
Moritz Lenz <moritz@cpan.org>
[ Top ]
[ Index of Synopses ]