I see no obvious reason why it shouldn't work. You may try using the multiple arguments version of system, though. From perldoc -f system:

If there is only one scalar argument, the argument is checked for shell metacharacters, and if there are any, the entire argument is passed to the system's command shell for parsing

But while we're here I feel like repeating the (now) daily question: why don't you make mycode.pl into a real module?

Ok, actually the system call is run under Acme::Spork.
Could it be the cause?

use Acme::Spork;
 my $req_id =  spork( sub { system("perl mycode.pl -email \"$uemail\" 
+-type $sometype  -unit $someunit"); } )
or die qq {Could not fork for spork: $!};
[download]

I can't turn  mycode.pl into a real module. Coz in real situation it is a executable binary.

I don't know anything abour Acme::Spork, so I can't guess if it's the problem or not. But if you remove it from the equation, and use the system call normally, do you have the same problem? If removing it corrects the problem, I would contact the author for assistance

Ok, actually the system call is run under Acme::Spork. Could it be the cause?

Easiest, securest way to find if Acme::Spork (never heard of it) is the cause: take it out of the equation and test it!

Just write:


#!/usr/bin/perl -w
use strict;

my $uemail = 'foo@bar.com';

system("perl mycode.pl -email \"$uemail\"") or die "Well, probably NOT
+ a spork problem";
[download]


or better yet, comment the spork line of your code and do a simple system call as above. Either way will tell you if this module is or is not the cause of your problem.

<UPDATE> My apologies to HuckinFappy. I ended up answering the same thing...</UPDATE>

Just my two cents.


---
Er Galvão Abbott
www.galvao.eti.br
Porto Alegre Perl Mongers

There doesn't seem to be any good reason why that wouldn't work.

How are you accessing the arguments inside mycode.pl? Have you tried looking at the contents of @ARGV as soon as the program starts up?

I use Getop::Long to get the argument.
I've looked at @ARGV, it gives:

$VAR1 = [ '-type', 'sugar', '-unit', '6' ];

# where

$sometype = 'foo';
$some_unit = 6;
[download]

So as you can see EMAIL option and its value is totally unrecognize here.
My overall construct under 'mycode.pl' looks like this:

use strict;
use Data::Dumper;        
use Getopt::Long;


print Dumper \@ARGV ;

my $type = 'bar';
my $no_unit   =  1;
my $help = 0;
my $tg_email = '';


if ( @ARGV == 0 ) {
    &usage();
    exit(1);
}
        
my $res = GetOptions ( "type=s"=>\$type,
                       "unit=i"=>\$no_unit,      
                       "email=s"=>\$tg_email,      
                       "help"=>\$help,);         

if ($res) {

     print "$tg_email\n" # show nothing here.

    # and do some other thing
    
}
[download]

How strange! Running the following with no arguments

#!/usr/bin/perl -l

use strict;
use warnings;
use Data::Dumper;

if (@ARGV) {
    print Dumper \@ARGV;
} else {
    my $email = 'myemail@gmail.com';
    system "$0 -email $email";
    print '-' x 20;
    system $0, -email => $email;
}

__END__
[download]

I get:

$VAR1 = [
          '-email',
          'myemail@gmail.com'
        ];

--------------------
$VAR1 = [
          '-email',
          'myemail@gmail.com'
        ];
[download]

my $receipt_email = 'myemail@gmail.com"
[download]

Mismatched quote types.

You also didn't share what shell you're using. Single vs double-quotes (and other characters) have big differences on CMD.EXE vs bash vs other command line shells.