in reply to Reading command line switches

Please clarify: Do you mean print to <STDOUT>, a log, or dead trees? Is there some reason use of the mark-one eyeball (and perhaps, Win's command line editing capabilities) is inadequate?

And what is the point of cating the pointless code in try.pl?

Replies are listed 'Best First'.
Re^2: Reading command line switches
by Just in (Sexton) on Mar 16, 2011 at 02:42 UTC

    I would like access to the switches, printing is irrespective. However, if it is of importance then STDOUT is a good place for it.

    cat was purely meant as an FYI to suggest that I did look in @ARGV before posting. In fact dare I say, it also suggests STDOUT, (negat|answer)ing your first question.

    The code will be executed by other people, and they might put any number of perl switches in on the command line which I would like to be able to determine.