in reply to Command line switches with Perl2Exe

To answer your question with another question, have you tried it? It should not take you long to write a short perl example, use Perl2Exe (assuming you have it) to convert it to an executable and test it. Failing that check the Perl2Exe documentation. I am sure you could have found the answer by trying a short example in less time that it would take to get a response here.

Hope this helps

Update: slight rewording

Martin
  • Comment on Re: Command line switches with Perl2Exe

Replies are listed 'Best First'.
Re^2: Command line switches with Perl2Exe
by hookandsling (Initiate) on Nov 09, 2007 at 13:23 UTC
    Thanks for the response
    Yes I have - I currently have a script that requires two input variables from the user. These are gathered using STDIN in perl world.
    However I need to compile this to a Windows binary - which works, but the program runs as usual (as you would expect) where the app waits for the input on the command line.

    e.g. c:\MyBinary.exe <CR>parameter1<CR>parameter2<CR>output!

    I need it to accept switches as per my previous example.

    I do realize this is a lame question from a Perl newbie - but I have been searching for this information for several hours without success (including the docs for perl2exe, the lama and Perl Monks - if this is not a suitable question for this board I apologise.
      Okay I answered my own question eventually.
      For any other new folks - it looks like the module Getopt::Std will do the trick.

        Basically, command line parameter/switch handling is no different under Perl2Exe than it is under Perl itself (perl.exe). All command line parameters are collected in the @ARGV array and there are modules like Getopt::Long that help you conveniently separate switches, values and parameters.

        Personally, I discourage you from using Getopt::Std, because it was written by TheDamian for his book Perl Best Practices and has seen no widespread use outside of that. 1 Getopt::Long, together with Pod::Usage is what I use to handle documentation and command line switches.

        Update: 1 I was thinking of Getopt::Euclid resp. Class::Std, neither of which are recommendable IMO.