Getopt::Casual - A casual replacement for other Getopt modules and -s.


  use Getopt::Casual;

  print $_, ' = ', $ARGV{ $_ }, "\n" for keys %ARGV 
    if $ARGV{ '--demo' };

  (see F<>)

  #-- Using import() to create casual defaults.

  perl C<->e 'use Getopt::Casual qw/ --debug=2 C<-l> C<-t> /; 
    print "$_ = $ARGV{ $_ }\n" for keys %ARGV' C<-t> foo

  --debug = 2
  -t = foo
  -l = 1


The Getopt::Casual module simplifies the manipulation of command line arguments in what should be a familiar way to most UNIX command line utility users. The following basic rules explain the assumptions that the &casual() makes for either &import() or @ARGV command line processing:

1) Arguments can be single characters or and combination of characters, although depending on your shell, some characters will be interpreted by the shell.

2) Arguments that begin with a '-' followed by a string, which can include spaces if the string is enclosed by quotes or double quotes, will have the value of that string. See Rule 3.

3) Arguments that begin with a '-' followed by another string that begins with a '-', including quoted strings that contain spaces, will have a value of 1.

4) Arguments that do not begin with a '-' will have a value of one. When preceded by an odd number of arguments that begin with a dash, this string is a value of the previous command line argument.

5) Arguments that begin with a '--' have a value of one. (See Rule 7)

6) The string '--' will terminate command line processing.

7) If the string contains an '=', the part of the string preceding the first '=' will be a key of %ARGV and the value will be the part following the first '=' until the end of that element of @ARGV.

8) All arguments of the script can be found as either a key or a value of %ARGV.

The same set of rules apply to the arguments you pass the import() subroutine.


See the included program called


If you find one, please tell me or supply a patch.


Getopt::Std, Getopt::Long


There has been some doubt as to whether or not this was useful enough to have to remember to tote it with you to every system on which you had command line perl scripts. The obvious advantage of the core modules is that they are wherever perl is installed. If portablity is really a key issue, use the core modules.


Daniel M. Lipton <>