bulk88 has asked for the wisdom of the Perl Monks concerning the following question:

@ARGV gives you the arguments from the command line that came after the script name. How do you from inside a script get the cmd line arguments that appeared before the script name when the script was executed?

example 
perl -MFoo::Module -I./specialib scriptname.pl --argv_arg

[download]
scriptname.pl needs to do a system($^X, and pass the same exact -I and -M arguments to the child perl process. The names of modules loaded with the -M are random and not from a fixed list from the viewpoint of scriptname.pl. Looking at @INC and %INC is a problem because of unpredictable PERL5LIB/PERLLIB/PERL5DB/interp compile options.

scriptname.pl is really a Makefile.PL that calls EUMM, and I'm trying to fix a problem in EUMM, where the makefile that EUMM generates determines it is out of date and regenerates itself (it=makefile), that makefile, doesn't call Makefile.PL with the same interp args (-Is and -Ms) that the 1st Makefile.PL run was called with, so the regenerated makefile is very different from the 1st makefile, which then breaks the compiling process.

Replies are listed 'Best First'.
Re: getting called with interpreter arguments, not script arguments, not @ARGV
by BrowserUk (Patriarch) on Jul 10, 2013 at 22:58 UTC

    On windows you can use GetCommandLine() to obtain the full command line used to invoke perl.exe.

    With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]
Re: getting called with interpreter arguments, not script arguments, not @ARGV
by thomas895 (Deacon) on Jul 10, 2013 at 22:51 UTC

    Why not just set scriptname.pl to executable(if not on Windows), and then pass the additional libs to load on the command line? The same applies to the include dirs.
    For example, consider the following: 

    my @modules = split ",", $ARGV[0];
my @paths   = split ":", $ARGV[1]; #change to ';' or other on Windows,
+ if needed

push(@INC, @paths);

$@ = undef;
map { eval("require $_;") unless $@ } @modules;
if($@) {
        die "one or more modules failed: $@";
}

#rest of script

    [download]
    ~Thomas~ 
    
"Excuse me for butting in, but I'm interrupt-driven..."
[reply]
[d/l]
Re: getting called with interpreter arguments, not script arguments, not @ARGV ( Devel::PL_origargv )
by Anonymous Monk on Jul 10, 2013 at 23:07 UTC
[reply]

Back to Seekers of Perl Wisdom