TIAS. YMMV

Different command shells handle quotes differently. The rules for Windows are quite different (in subtle ways) than those for *nix for example. However pretty much all command shells generate an argument array - an array of strings that corespond to the "arguments" passed on the command line. If the arguments contain various special characters they need to be quoted. But the kind shell removes the quotes for you. After all, all you really want are the arguments right?

If you really need the quotes, put em back. If you need to distinguish between an argument that was quoted and one that wasn't, then you are pretty much stuffed unless you quote the quotes.

Dang. Thought so. So I guess I could say that for tool foo, if there is an argument "-s", that I need to add quotes around the following argument. Guess that's the way to handle it.

Thanks,
Shannon Kerr

First off, please don't put your text inside the markers for your sig. Some people turn off sigs, and won't see anything here.

Second, the way the shell operates is that the quotes are special characters. That's not using your program, that's using a shell. Learning to use the shell means that you'll learn to use backslashes as appropriate to get the meaning you want across. Whether that's a good thing or bad may depend on what you want to accomplish ;-)

I'm kinda curious as to why you need quotes passed through, though.

Thanks for the tip on the sig. My fault for not reading clearly. Fixed it now.

Need the quotes because I'm passing @ARGV through a tcp socket. There won't always be quotes, so when they are there, I need to keep them so they can be passed.

I could process @ARGV looking for the "-s" and add quotes around the following argument, but I'd like to avoid that.
Thanks,
Shannon Kerr

Since your primary concern is passing the arguments on correcty, why not do:

@ARGV = map { quotemeta($_) } @ARGV;
print "@ARGV";

__OUTPUT__
>  perl test.pl -s "1 2 3"
\-s 1\ 2\ 3
[download]

For bash-like shells, quotemeta doesn't do the correct escaping, as it turns a newline to a backslash-newline pair, which bash will unescape to an empty string.

Escaping your quotes *should* work every-where. Works for me on *nix, Cygwin and Dos-

  foo.pl -s \"1 2 3\"
[download]

Ignore me I was smoking happy weed that just gives you a quote on the beginning of one argument and the end of the other, serve me right for testing by doing a print " [@ARGV]"...