in reply to Parsing strings into @ARGV

You don't say WHICH shell you're talking about. Different shells will interpret command-line contents differently, and produce different underlying (char*)argv[] results (which Perl imports into @ARGV).

On Windows, different C compilers (used to build the Perl.EXE interpreter) may even introduce variations, since the runtime library can re-interpret the (char*)argv[] to support filename globbing or other extended features.

--
[ e d @ h a l l e y . c c ]

Replies are listed 'Best First'.
Re: Re: Parsing strings into @ARGV
by mirod (Canon) on Apr 23, 2004 at 15:00 UTC

    I know, I mentionned that. Basically I just want to be able to use "regular" arguments and quoted, or double-quoted ones. I don't think that's subject to too much variation, at least in the *nix world. I use bash usually BTW.