in reply to @ARGV being corrupted

If it hurts when you do that, don't do that. Instead, as the other Wise Ones have said, look at Getopt::Std. There's no excuse to re-invent that wheel, not even "that's the way we've always done it!" :)

Replies are listed 'Best First'.
Re^2: @ARGV being corrupted
by Anonymous Monk on Jul 22, 2004 at 14:39 UTC
    This fails on both Solaris ( not sure the version at this time ) and Windows 2000 . Using Perl version 5.6.1 . The line of code did detect the option but my previous detect for -V does that too, I will look and see how I can gather the "devl" specification.
[reply]
      Found the problem. Since this is utilized across platforms someone must have modified it on windows. had the ^M characters on the ending lines. removed them and it worked.
[reply]

        When you transfer a script across OS platforms, unless it is transferred via FTP in ASCII mode, it will suffer from the fact that one OS uses different line endings than another. And perl (the executable) doesn't know how to deal with a shebang line that looks like: #!/usr/bin/perl^M.

        This is further exhaserbated by the fact that you were dealing with @ARGV. That special variable takes its values from the command line. The command line can be a combination of what was typed when the script was run, as well as what was on the shebang line.

        Don't forget to transfer in ASCII mode, and when you do forget, be sure to run unix2dos or dos2unix to fix the line endings.


        Dave

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom