Command-line arguments: Difference between revisions

 

myprogram -c "alpha beta" -h "gamma"

 

=={{header|Ada}}==

In Ada95 and later versions, command line arguments are available through the predefined package Ada.Command_Line. In Ada83, this would be implementation dependent.

 

with Ada.Text_IO; use Ada.Text_IO;

 

end loop;

New_Line;

 

=== Alternative version using Matreshka ===

Uses [http://forge.ada-ru.org/matreshka Matreshka]

 

 

with League.Application;

(League.Application.Arguments.Element (J).To_Wide_Wide_String);

end loop;

 

=={{header|Aikido}}==

The arguments are passed to the program as a vector of strings called <em>args</em>

 

foreach arg in args {

}

 

 

=={{header|Aime}}==

 

i = 0;

o_byte('\n');

i += 1;

 

=={{header|ALGOL 68}}==

{{works with|ALGOL 68G|Any - tested with release mk15-0.8b.fc9.i386 - ''argc'' and ''argv'' are not part of the standard's prelude}}

FOR i TO argc DO

printf(($"the argument #"g(-0)" is "gl$, i, argv(i)))

OD

Linux command:

/usr/bin/a68g Command-line_arguments.a68 - 1 2 3 ...

the argument #6 is 3

the argument #7 is ...

</pre>

 

=={{header|AppleScript}}==

 

#!/usr/bin/env osascript

-- Print first argument

return (item 1 of argv)

end run

 

=={{header|AutoHotkey}}==

From the AutoHotkey [http://www.autohotkey.com/docs/Scripts.htm documentation]:

"The script sees incoming parameters as the variables %1%, %2%, and so on. In addition, %0% contains the number of parameters passed (0 if none). "

params .= %A_Index% . A_Space

If params !=

MsgBox, %0% parameters were passed:`n`n %params%

Else

 

=={{header|AWK}}==

 

 

BEGIN {

print "Argument " l " is " ARGV[l]

}

 

=={{header|Babel}}==

Invoke Babel in interactive mode with arguments using the -i switch:

 

 

Print the argv list with newlines:

 

 

{{out}}

Print the argv list with spaces:

 

 

{{out}}

To access an individual argument, use the ith operator to select an element from the argv list; print with newline using say:

 

 

{{out}}

For most older BASICs that supply the keyword <code>COMMAND$</code>, all arguments are returned in a single string that must then be parsed inside the program. (Unlike modern BASICs, there is often no easy way to retrieve the program's name.)

 

 

Sample output:

FreeBASIC supplies three ways to retrieve the arguments: <code>COMMAND$</code> (which works identically to QuickBASIC's <code>COMMAND$</code>), <code>COMMAND$()</code> (a string array which works like [[#C|C]]'s <code>argv[]</code>), and <code>__FB_ARGV__</code> (an array of pointers which works even more like C's <code>argv[]</code>) and __FB_ARGC__ (which works like C's <code>argc</code>).

 

 

PRINT COMMAND$

FOR i = 0 TO __FB_ARGC__ - 1

PRINT "arg "; i; " = '"; *__FB_ARGV__[i]; "'"

 

Sample output:

 

==={{header|BaCon}}===

PRINT "Entire command line: ", ARGUMENT$

 

PRINT " " & cli$[i];

NEXT

 

{{out}}

=={{header|Batch File}}==

{{works with|Windows NT|4 or later (includes Windows XP and onward)}}

setlocal enabledelayedexpansion

 

for /l %%a in (1,1,%count%) do (

echo !parameter[%%a]!

 

Another way of doing it

 

@echo off

setlocal enabledelayedexpansion

for /l %%i in (1,1,%p#%) do (

echo p%%i=!p%%i!

 

Invocation:

 

fn=d:\bin\args2.cmd

p0=args2

p2=bar baz

p3=quux

 

=={{header|BBC BASIC}}==

{{works with|BBC BASIC for Windows}}

 

=={{header|Bracmat}}==

When Bracmat is started with one or more arguments, each argument is evaluated as if it were a Bracmat expression <i>unless</i> an argument (for example the first one) consumes the next argument(s) by calling <code>arg$</code>. Each invocation of <code>arg$</code> pops one argument from the remaining list of arguments. Calling <code>arg$</code> when no more arguments are available results in failure. The following program iterates over all arguments following the currently evaluated argument and outputs the argument to standard output.

Now run Bracmat with this program as the first argument in a DOS environment:

<pre>bracmat "whl'(arg$:?a&out$(str$(\"next arg=\" !a)))" "a" /b -c 2+3 'd;' "out$(\"13+7=\" 13+7)"</pre>

Be careful on systems that use Unicode or other multibyte character sets. You may need to use a type of _wchar* and multi-byte-character-set-aware versions of printf.

 

#include <stdio.h>

 

(void) printf("the argument #%d is %s\n", i, argv[i]);

return EXIT_SUCCESS;

 

=={{header|C sharp|C#}}==

There are at least two methods to access the command-line arguments. The first method is to access the string array passed to Main. This method only accesses the arguments and not the path to the executable.

 

namespace RosettaCode {

}

}

 

The second method is to call the Environment.GetCommandLineArgs function. This method also returns the path to the executable as args[0] followed by the actual command line arguments.

 

namespace RosettaCode {

}

}

 

=={{header|Clean}}==

<tt>getCommandLine</tt> from the module <tt>ArgEnv</tt> returns an array of command-line arguments (the first element is the name of the program).

 

 

 

=={{header|Clojure}}==

The value of ''*command-line-args*'' is a sequence of the supplied command line arguments, or ''nil'' if none were supplied.

 

 

=={{header|COBOL}}==

 

Getting the arguments in one go, exactly as they were passed in:

PROGRAM-ID. accept-all-args.

GOBACK

 

Getting the arguments one at a time, with arguments being split by whitespace if not in quotes:

PROGRAM-ID. accept-args-one-at-a-time.

GOBACK

 

=={{header|CoffeeScript}}==

{{works with|Node.js}}

console.log arg for arg in process.argv

 

=={{header|Common Lisp}}==

The following function could be used to create a uniform way to access the arguments:

 

(or

#+clisp (ext:argv)

#+allegro (sys:command-line-arguments)

#+lispworks sys:*line-arguments-list*

 

=={{header|D}}==

import std.stdio;

 

foreach (immutable i, arg; args[1 .. $])

writefln("#%2d : %s", i + 1, arg);

=={{header|DCL}}==

case is not preserved unless the parameter is in quotes

$ loop:

$ write sys$output "the value of P''i' is ", p'i

$ i = i + 1

{{out}}

<pre>$ @command_line_arguments -c "alpha beta" -h "gamma"

the value of P7 is

the value of P8 is</pre>

 

=={{header|Déjà Vu}}==

Command line arguments are found in <code>!args</code> and <code>!opts</code>.

 

print\( "Argument #" i " is " )

. get-from !args i

 

if has !opts :four:

{{out}}

<pre>$ vu args-3.deja one two -c three --four=five

The order of command line ''options'' is lost.

 

 

 

 

 

 

=={{header|E}}==

 

 

=={{header|Eiffel}}==

This class inherits functionality for dealing with command line arguments from class <code lang="eiffel">ARGUMENTS</code>. It uses the feature <code lang="eiffel">separate_character_option_value</code> to return the values by option name for each of the two arguments.

 

APPLICATION

inherit

io.read_line -- Keep console window open

end

 

Output (for command line arguments: -c "alpha beta" -h "gamma"):

 

=={{header|Elena}}==

 

=={{header|Elixir}}==

Elixir provides command line arguments via the <tt>System.argv()</tt> function.

IO.puts 'Arguments:'

Example run:

Arguments:

a

b=2

--3

 

=={{header|Emacs Lisp}}==

 

=={{header|Erlang}}==

When used as a script language the arguments is a list to the main/1 function. When compiled use init:get_arguments/0

result

{progname,["erl"]},

{home,["/home/me"]},

{c,["alpha beta"]},

 

init:get_argument(name) can be used to fetch value of a particular flag

 

{ok,[["gamma"]]}

5> init:get_argument(c).

 

=={{header|Euphoria}}==

printf(1,"Interpreter/executable name: %s\n",{cmd[1]})

printf(1,"Program file name: %s\n",{cmd[2]})

printf(1,"#%d : %s\n",{i,cmd[i]})

end for

 

=={{header|F_Sharp|F#}}==

The entry-point function accepts the comment line arguments as an array of strings. The following program will print each argument on a separate line.

[<EntryPoint>]

let main args =

Array.iter (fun x -> printfn "%s" x) args

=={{header|Factor}}==

USING: io sequences command-line ;

 

=={{header|Fancy}}==

a println # print each given command line argument

 

=={{header|Fantom}}==

 

class Main

{

}

}

 

=={{header|Forth}}==

 

{{works with|gforth|0.6.2}}

: main

argc @ 0 do i arg type cr loop ;

 

 

Here is output from a sample run.

gforth

args.f

beta gamma

delta

=={{header|Fortran}}==

{{works with|Fortran|2003 and later}}

 

implicit none

 

end program command_line_arguments

Note: This sample uses the Fortran 2003 intrinsic routines <code>command_argument_count</code> and <code>get_command_argument</code> instead of the nonstandard extensions <code>iargc</code> and <code>getarg</code>. Most Fortran compilers support both.

 

Sample usage:

./a.out

-c

alpha beta

-h

 

=={{header|FreeBASIC}}==

 

' Program (myprogram.exe) invoke as follows:

Print

Print "Press any key to quit"

 

{{out}}

=={{header|Frink}}==

Arguments to a program are available in the <CODE>ARGS</CODE> array variable.

println[ARGS]

 

=={{header|FunL}}==

 

=={{header|Gambas}}==

DIM l AS Integer

DIM numparms AS Integer

PRINT l; " : "; parm

NEXT

 

=={{header|Go}}==

import (

)

 

func main() {

 

=={{header|Groovy}}==

Command-line arguments are accessible via the '''args''' list variable. The following is saved as the file "Echo.groovy":

 

The existence of command-line arguments presupposes the existence of a command line interpreter. The following test runs were entered in a cygwin bash shell in a Microsoft Windows XP system:

=={{header|Harbour}}==

Uses the Harbour-specific hb_PValue() function

 

LOCAL i

NEXT

 

 

=={{header|Haskell}}==

 

myprog.hs:

<pre>

myprog a -h b c

 

=={{header|HicEst}}==

EDIT(Text=$CMD_LINE, SePaRators='-"', ITeM=i, IF ' ', EXit, ENDIF, Parse=cmd, GetPosition=position)

IF(position > 0) WRITE(Messagebox) cmd

 

=={{header|Icon}} and {{header|Unicon}}==

Command line parameters are passed to Icon/Unicon programs as a list of strings.

every write(!arglist)

 

{{libheader|Icon Programming Library}} includes [http://www.cs.arizona.edu/icon/library/procs/options.htm options] that parses the command line as switches and arguments and returns the results in a table.

 

=={{header|Io}}==

 

=={{header|Ioke}}==

 

=={{header|J}}==

The global <code>ARGV</code> holds the command line arguments. Thus, a program to display them:

 

 

 

public static void main(String[] args) {

System.out.println("There are " + args.length + " arguments given.");

System.out.println("The argument #" + (i+1) + " is " + args[i] + " and is at index " + i);

}

 

For more sophisticated command-line option and option-argument parsing use the [http://commons.apache.org/cli '''Apache Commons CLI'''] (command-line interface) library.

 

=={{header|JavaScript}}==

{{works with|JScript}}

for (var i = 0; i < objArgs.length; i++)

{{works with|JScript.NET (compiled with jsc.exe)}}

var argv:String[] = Environment.GetCommandLineArgs();

for (var i in argv)

{{works with|Rhino}}

{{works with|SpiderMonkey}}

 

=={{header|jq}}==

$ jq -n '$ARGS' --args a b

 

"positional": [

"a",

],

"named": {}

 

Arguments specified with ''--args'' are always read as JSON strings; arguments specified with ''--jsonargs''

}</pre>

 

 

=={{header|Julia}}==

 

println(prog, "'s command-line arguments are:")

println(" ", s)

end

 

{{out}}

gamma

</pre>

 

=={{header|Kotlin}}==

{{trans|Java}}

println("There are " + args.size + " arguments given.")

args.forEachIndexed { i, a -> println("The argument #${i+1} is $a and is at index $i") }

{{out}}

See Java output.

 

=={{header|Lasso}}==

 

iterate($argv) => {

stdoutnl("Argument " + loop_count + ": " + loop_value)

Output:

Argument 1: arguments.lasso

Argument 2: -c

Argument 3: alpha beta

Argument 4: -h

 

=={{header|LFE}}==

 

To demonstrate this, we can start the LFE REPL up with the parameters for this example:

$ ./bin/lfe -pa ebin/ -c "alpha beta" -h "gamma"

 

Once we're in the shell, we can get all the initializing arguments with this call:

> (: init get_arguments)

(#(root ("/opt/erlang/r15b03"))

#(c ("alpha beta"))

#(h ("gamma")))

 

We can also get specific arguments if we know their keys:

> (: init get_argument 'c)

#(ok (("alpha beta")))

> (: init get_argument 'h)

#(ok (("gamma")))

 

=={{header|Liberty BASIC}}==

 

=={{header|Lingo}}==

 

In latest versions of Mac OS X, the above approach doesn't work anymore. But there is a free "Xtra" (binary plugin/shared library) called "CommandLine Xtra" that works both in Windows and Mac OS X and returns the command-line parsed into a lingo list (array):

 

{{libheader|CommandLine Xtra}}

 

=={{header|Logo}}==

logo file.logo - arg1 arg2 arg3

Then the arguments after the "-" are found in a list in variable :COMMAND.LINE

Alternatively, make the first line of an executable logo script:

#! /usr/bin/logo -

 

=={{header|LSE64}}==

0 # argument

dup arg dup 0 = || ,t 1 + repeat

=={{header|Lua}}==

 

The lua scripting language does not use argc and argv conventions for the command line parameters. Instead, the command line parameters to the main script are provided through the global table arg. The script name is placed into element zero of arg, and the script parameters go into the subsequent elements:

 

 

print "Arguments:"

for i = 1, #arg do

print( i," ", arg[i] )

 

myprogram:

Output:

<pre>{myprogram,-c,alpha beta,-h,gamma}</pre>

 

=={{header|Mercury}}==

:- module cmd_line_args.

:- interface.

print_arg(Arg, ArgNum, ArgNum + 1, !IO) :-

io.format("the argument #%d is %s\n", [i(ArgNum), s(Arg)], !IO).

 

=={{header|MMIX}}==

argc IS $0

i IS $2

TRAP 0,Halt,0

 

 

=={{header|Modula-2}}==

 

FROM Arguments IMPORT GetArgs, ArgTable, GetEnv;

INC (item)

UNTIL item = count

Example:

jan@Beryllium:~/modula/test$ try jantje zag eens pruimen hangen

Count = 6

4 : pruimen

5 : hangen

 

=={{header|Modula-3}}==

Command line parameters are accessed using the <tt>Params</tt> module.

 

IMPORT IO, Params;

END;

END;

 

Output:

20

</pre>

 

=={{header|Nemerle}}==

using System.Console;

 

foreach (cl_arg in cl_args) Write($"$cl_arg ");

}

 

=={{header|NetRexx}}==

In a stand-alone application NetRexx places the command string passed to it in a variable called <tt>arg</tt>.

-- sample arguments: -c "alpha beta" -h "gamma"

say "program arguments:" arg

'''Output:'''

<pre>

 

=={{header|Nim}}==

 

=={{header|Oberon-2}}==

{{works with|oo2c}}

MODULE CommandLineArguments;

IMPORT

Out.String("4.-: ");Out.String(Args.AsString(4));Out.Ln

END CommandLineArguments.

{{out}}

<pre>

 

=={{header|Objeck}}==

}

}

 

=={{header|Objective-C}}==

 

In addition to the regular C mechanism of arguments to main(), Objective-C also has another way to get the arguments as string objects inside an array object:

NSLog(@"This program is named %@.", [args objectAtIndex:0]);

NSLog(@"There are %d arguments.", [args count] - 1);

for (i = 1; i < [args count]; ++i){

NSLog(@"the argument #%d is %@", i, [args objectAtIndex:i]);

 

=={{header|OCaml}}==

The program name is also passed as "argument", so the array length is actually one more than the number of program arguments.

 

Printf.printf "This program is named %s.\n" Sys.argv.(0);

for i = 1 to Array.length Sys.argv - 1 do

Printf.printf "the argument #%d is %s\n" i Sys.argv.(i)

 

let somebool = ref false

let somestr = ref ""

(fun x -> raise (Arg.Bad ("Bad argument : " ^ x)))

usage;

 

 

 

 

 

=={{header|Oforth}}==

The first argument is the program name, so this list is never empty.

 

 

=={{header|Oz}}==

===Raw arguments===

Like in C, but without the program name:

import Application System

define

{ForAll ArgList System.showInfo}

{Application.exit 0}

 

===Preprocessed arguments===

import Application System

define

{System.showInfo Args.h}

{Application.exit 0}

 

=={{header|Pascal}}==

 

=={{header|Perl}}==

@ARGV is the array containing all command line parameters

 

my $params_size = @ARGV;

my $second = $ARGV[1];

 

If you don't mind importing a module:

 

GetOptions (

'help|h' => \my $help,

'verbose|v' => \my $verbose,

 

=={{header|Phix}}==

When interpreting, the first two elements returned by command_line() are {interpreter,source}.<br>

When compiled, the first two elements are instead {executable,executable}, so the parameters (if any) are consistently the 3rd element onwards.

{{out}}

<pre>

C:\Program Files (x86)\Phix>p testcl -c "alpha beta" -h "gamma"

#6 : gamma

C:\Program Files (x86)\Phix>

</pre>

 

When PHP is run from the command line, the special variables <tt>$argv</tt> and <tt>$argc</tt> contain the array of arguments, and the number of arguments, respectively. The program name is passed as the first argument.

 

$program_name = $argv[0];

$second_arg = $argv[2];

$all_args_without_program_name = array_shift($argv);

 

=={{header|PicoLisp}}==

and then '[http://software-lab.de/doc/refL.html#load load]' all remaining

command line arguments.

 

(de c ()

 

(load T)

Output:

<pre>$ ./myprogram -c "alpha beta" -h "gamma"

 

=={{header|PL/I}}==

/* The entire command line except the command word itself is passed */

/* to the parameter variable in PL/I. */

 

end program;

 

=={{header|Pop11}}==

variable poparglist contains list of command line arguments (as strings). One can use iteration over list to process then (for example print).

 

for arg in poparglist do

printf(arg, '->%s<-\n');

 

=={{header|PowerBASIC}}==

For versions of PowerBASIC prior to [[PB/Win]] 9 and [[PB/CC]] 5, the only option available is identical to the one used by [[#BASIC|QuickBASIC]] above:

 

Current versions of PowerBASIC (with the likely exception of [[PB/DOS]]) include <code>COMMAND$()</code> that works similarly to [[FreeBASIC]]'s <code>COMMAND$()</code>, except that you can't retrieve the application's name:

? COMMAND$

? COMMAND$(0)

PRINT "The argument "; i; " is "; COMMAND$(i)

i = i + 1

 

=={{header|PowerShell}}==

In PowerShell the arguments to a script can be accessed with the <code>$args</code> array:

foreach ($s in $args) {

Write-Host Argument (++$i) is $s

 

=={{header|Pure}}==

Arguments are in global variables, argc and argv.

 

using system;

 

printf "There are %d command line argumants\n" argc;

puts "They are " $$ map (puts) argv;

 

=={{header|PureBasic}}==

===Reading all parameters===

You can easily read all parameters by using ProgramParameter() without argument.

Define n=CountProgramParameters()

PrintN("Reading all parameters")

Input()

CloseConsole()

===Reading specific parameters===

You can specify which parameter 'n' to read.

Define n

PrintN("Reading specific pameters")

Input()

CloseConsole()

 

=={{header|Python}}==

''sys.argv'' is a list containing all command line arguments, including the program name. Typically you slice the list to access the actual command line argument:

 

program_name = sys.argv[0]

arguments = sys.argv[1:]

 

When running a module by invoking Python, the Python interpreter processes and removes some of the arguments, and the module cannot access them. To process command line arguments, run the module directly. sys.argv is a copy of the command line arguments; modifying sys.argv will not change the arguments seen by other processes, e.g. ps. (In other words sys.argv is an object which contains a copy of the process' command line arguments ... modifying that copy is only visible from within the Python program and not externally).

Suppose you want to call your script <tt>test.r</tt> with the arguments <tt>a=1 b=c(2,5,6)</tt>, where <tt>b</tt> is a numeric vector. Suppose you also want to redirect your output to <tt>test.out</tt> (not that you have a choice--I still don't know how to make R send shell-script output to stdout). You would then run

 

 

from the commandline, with the following text in <tt>test.r</tt>:

 

args <- (commandArgs(TRUE))

 

}

print(a*2)

 

(possibly preceding code that actually does something :-) Your output <tt>test.out</tt> would then contain (e.g., if you <tt>cat</tt> it)

The following is the simplest program that prints the command-line arguments:

 

 

You can also explicitly print each argument to standard output:

 

 

 

=={{header|RapidQ}}==

FOR i=1 TO CommandCount

PRINT "The argument "; i; " is "; Command$(i)

 

=={{header|Raven}}==

 

 

stack (6 items)

3 => "alpha beta"

4 => "-h"

 

=={{header|REALbasic}}==

For each arg As String In args

Stdout.WriteLine(arg)

Next

Output (given arguments: ''--foo !bar "bat bang"''):

appName.exe

=={{header|REXX}}==

The entire command line arguments (as a single string) are passed by REXX to the program.

Input:

 

only options that start with a minus (-) are to be examined

and assumed to be options.

/*another version: */

/* aaa=arg(1) */

say

say 'options='opts

 

;Note to users of Microsoft Windows and Regina REXX:

 

=={{header|Ring}}==

see copy("=",30) + nl

see "Command Line Parameters" + nl

see x + nl

next

 

=={{header|Ruby}}==

 

myprog:

 

myprog a -h b c

 

=={{header|Rust}}==

 

fn main(){

let args: Vec<_> = env::args().collect();

println!("{:?}", args);

Run:

 

=={{header|S-lang}}==

The command-line arguments exist in the array __argv:

foreach a (__argv)

print(a);

 

__set_argc_argv(new_argv);

 

=={{header|Sather}}==

main(args:ARRAY{STR}) is

loop

end;

end;

 

As in C (and others), the first element is the command itself (exactly as it is written in the command line and after shell variable expansion); e.g.

array of strings, and returns unit. That array contains the command line arguments.

 

println(s"Received the following arguments: + ${args.mkString("", ", ", ".")}")

 

When running a Scala script, where the whole body is executed, the arguments get stored in an array of strings called <code>argv</code>:

 

 

=={{header|Scheme}}==

 

 

=={{header|Seed7}}==

 

 

const proc: main is func

writeln("The argument #" <& i <& " is " <& argv(PROGRAM)[i]);

end for;

 

=={{header|Sidef}}==

Command line arguments are available in the ARGV array.

{{out}}

<pre>% myprog -c "alpha beta" -h "gamma"

 

=={{header|Slate}}==

 

=={{header|Smalltalk}}==

{{works with|GNU Smalltalk}}

(Smalltalk getArgv: i) displayNl

 

{{works with|Smalltalk/X}}

 

=={{header|Standard ML}}==

 

val args = CommandLine.arguments ();

Array.appi

(fn (i, x) => print ("the argument #" ^ Int.toString (i+1) ^ " is " ^ x ^ "\n"))

 

=={{header|Swift}}==

 

println("This program is named \(args[0]).")

println("There are \(args.count-1) arguments.")

for i in 1..<args.count {

println("the argument #\(i) is \(args[i])")

 

Alternately:

 

{{works with|Swift|1.2+}}

println("There are \(Process.argc-1) arguments.")

for i in 1 ..< Int(Process.argc) {

println("the argument #\(i) is \(String.fromCString(Process.unsafeArgv[i])!)")

{{works with|Swift|1.0-1.1}}

println("There are \(C_ARGC-1) arguments.")

for i in 1 ..< Int(C_ARGC) {

println("the argument #\(i) is \(String.fromCString(C_ARGV[i])!)")

 

=={{header|Tcl}}==

The predefined global variable <tt>argc</tt> contains the number of arguments passed to the program after the script being executed, <tt>argv</tt> contains those arguments as a list. (The name of the script is in the <tt>argv0</tt> global variable, and the name of the executable interpreter itself is returned by the command <code>info nameofexecutable</code>.) Retrieving the second argument might look something like this:

 

puts [lindex $argv 1]

 

(Tcl counts from zero, thus <tt>[lindex $list 1]</tt> retrieves the second item in the list)

number of arguments is provided by #args.

 

[ dup . char: = emit space ] is #=

 

=={{header|TXR}}==

This <code>@(next :args)</code> should be written as the first line of the TXR program, because TXR otherwise interprets the first argument as the name of an input file to open.

 

@(collect)

@arg

@(output)

My args are: {@(rep)@arg, @(last)@arg@(end)}

 

<pre>$ ./txr args.txr

Here is an example program which requires exactly three arguments. Note how <code>ldiff</code> is used to compute the arguments that are processed by TXR (the interpreter name, any special arguments and script name), to print an accurate usage message.

 

((a b c) (put-line "got three args, thanks!"))

{{out}}

<pre>$ txr command-line-args.txr 1 2

===[[Bourne Shell]]===

To retrieve the entire list of arguments:

To retrieve the second and fifth arguments:

 

=={{header|Ursa}}==

In Ursa, all command line arguments (including the program name as invoked) are contained in the string stream args.

# command-line arguments

#

for (decl int i) (< i (size args)) (inc i)

out args<i> endl console

 

Sample shell session in the Bourne shell:

This example application does nothing but display the data

structure on standard output.

 

#executable ('parameterized','')

 

Here is a bash terminal session.

<pre>$ clarg -c alpha,beta -h gamma --foo=bar,baz

 

args.v

 

./args.v a b c

 

=={{header|Visual Basic}}==

 

Like [[#BASIC|Qbasic]], Visual Basic returns all of the args in the built-in variable <code>Command$</code>:

MsgBox Command$

 

=={{header|Visual Basic .NET}}==

This syntax will tokenize the command line arguments. Tokens are normally delimited by spaces, but spaces can be part of a token if surrounded by quotes.

 

For Each token In args

Console.WriteLine(token)

Next

 

=={{header|zkl}}==

File myprogram.zkl:

zkl myprogram -c "alpha beta" -h "gamma"

{{out}}

{{omit from|Commodore BASIC}}

{{omit from|dc}}

{{omit from|GUISS}}

{{omit from|Lotus 123 Macro Scripting}}

{{omit from|PostScript}}

{{omit from|Retro}}

{{omit from|TI-89 BASIC|Does not have an external OS/command processor.}}

{{omit from|Vim Script}}