command line option order matters? 
Author Message
 command line option order matters?

Is it a feature or a bug that:

doesn't give the same result as:

(only thing that changed is -ne became -en)

goth 578% perl -v
This is perl, version 5.0, Beta 3f

goth 579% uname -a
IRIX goth 5.2 02282016 IP22 mips
Kevin Luster, Project Reality | Silicon Graphics MS-880
Kicking Sega's {*filter*}          | 2011 N. Shoreline Blvd

http://www.*-*-*.com/ ~kluster/Visigoth.html

Fri, 18 Jul 1997 11:56:42 GMT  
 command line option order matters?
   Is it a feature or a bug that:

   doesn't give the same result as:

Im not sure I'd call it either.  It is a documented performance though.
The 'e' command line switch takes an argument.  The Camel book (page 351)
says that switches which don't take arguments can be combined withthe
following switch.  Since e takes an argument it can't be combined with the
'n' following, or it treats it as an empty argument.


Varimetrix Corporation                          2350 Commerce Park Dr. Ste 4
Palm Bay, FL    32905                                   CAD/CAM/CAE/Software
(407) 676-3222                                           Fax: (407) 723-4388

Fri, 18 Jul 1997 23:44:37 GMT  
 [ 2 post ] 

 Relevant Pages 

1. Ordering of command line switches

2. command line switch ordering?

3. Problem checking if a command line option has been specified using Getopt::Long

4. ANNOUNCE: Getopt::Long 2.9 -- Universal command line options processing

5. - reads command line options

6. ANNOUNCE: Getopt::Long 2.6 -- Universal command line options processing

7. Command line options Input >Output how?

8. Trouble running Satan under Linux with command line options

9. Custom Makefile.PL command line options and recursive behavior

10. -S command line option

11. How to get command line options?

12. MacPERL Command Line Options


Powered by phpBB® Forum Software