LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Non-*NIX Forums > Programming
User Name
Password
Programming This forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.

Notices


Reply
  Search this Thread
Old 01-06-2010, 11:32 PM   #1
ashok.g
Member
 
Registered: Dec 2009
Location: Hyderabad,India
Distribution: RHEl AS 4
Posts: 215

Rep: Reputation: 32
How to get the total arguments in perl??


Hi,
How can I get the total arguments in perl.To be more specific if I try to execute the command
Code:
perl -w myperl.pl ash ok kumar
I should be able to get all the command line arguments.

I know that @ARGV will store only the arguments passed but not the entire arguments.
 
Old 01-07-2010, 12:03 AM   #2
bartonski
Member
 
Registered: Jul 2006
Location: Louisville, KY
Distribution: Fedora 12, Slackware, Debian, Ubuntu Karmic, FreeBSD 7.1
Posts: 443
Blog Entries: 1

Rep: Reputation: 48
Quote:
Originally Posted by ashok.g View Post
Hi,
How can I get the total arguments in perl.To be more specific if I try to execute the command
Code:
perl -w myperl.pl ash ok kumar
I should be able to get all the command line arguments.

I know that @ARGV will store only the arguments passed but not the entire arguments.
I'm not quite sure what you mean by "entire arguments" as opposed to "arguments passed". Are you looking for the number of arguments passed?

Code:
$ cat /tmp/myperl.pl
#!/usr/bin/perl

use strict;
use warnings;

print join(" ", @ARGV) . "\n";
print scalar @ARGV . "\n";

$ perl /tmp/myperl.pl one two three four
one two three four
4
If you are trying to get environment variables exported by the shell, try this:
Code:
$ cat myperl2.pl 
#!/usr/bin/perl

use strict;
use warnings;

print "the value of the environment variable \$USER is '$ENV{USER}'\n";
$ perl myperl2.pl 
the value of the environment variable $USER is 'tiger'
Please explain what you mean by "entire arguments" as opposed to "arguments passed".

Thanks!
 
Old 01-07-2010, 12:23 AM   #3
ashok.g
Member
 
Registered: Dec 2009
Location: Hyderabad,India
Distribution: RHEl AS 4
Posts: 215

Original Poster
Rep: Reputation: 32
Quote:
Originally Posted by bartonski View Post
I'm not quite sure what you mean by "entire arguments" as opposed to "arguments passed".
To be more clear....
Code:
#!usr/bin/perl -w
#Program to display the total arguments
use warnings;
use strict;
foreach (@ARGV)
{
print $_," ";
}
print "\n";
Now I run the command as:
Code:
[Ashok@station130 Assignment_1]$ perl -w package.pl ash ok kumar
ash ok kumar
[Ashok@station130 Assignment_1]$
What my requirement is I want to the output as:
Code:
[Ashok@station130 Assignment_1]$ perl -w package.pl ash ok kumar
perl -w package.pl ash ok kumar
[Ashok@station130 Assignment_1]$
I think it's very clear now....
 
Old 01-07-2010, 04:05 AM   #4
ashok.g
Member
 
Registered: Dec 2009
Location: Hyderabad,India
Distribution: RHEl AS 4
Posts: 215

Original Poster
Rep: Reputation: 32
Also, there is a special variable $0 which can be used to get our program name. But what about rest of the arguments(perl -w)?
 
Old 01-07-2010, 05:18 PM   #5
bartonski
Member
 
Registered: Jul 2006
Location: Louisville, KY
Distribution: Fedora 12, Slackware, Debian, Ubuntu Karmic, FreeBSD 7.1
Posts: 443
Blog Entries: 1

Rep: Reputation: 48
Ahh. I see. The problem is that your perl script doesn't actually see the entire command line.

The shell sees

Code:
perl -w package.pl ash ok kumar
perl sees

Code:
-w package.pl ash ok kumar
[and knows that it is being called as 'perl'].

Package.pl sees

Code:
ash ok kumar
[and knows that it is being called as 'Package.pl']

For Package.pl to be able to see the entire command line, it's going to have to make a call back to the shell. The shell has a variable '$COMP_LINE' contains the entire command line, but it's not populated by default... I didn't have time to read the entire section in the Bash man pages about this, but I know that it's there.

Alternatively, /proc/$$/cmdline is a virtual file which contains the command line.
 
Old 01-07-2010, 07:36 PM   #6
smeezekitty
Senior Member
 
Registered: Sep 2009
Location: Washington U.S.
Distribution: M$ Windows / Debian / Ubuntu / DSL / many others
Posts: 2,339

Rep: Reputation: 231Reputation: 231Reputation: 231
Code:
use warnings;
open f, '/proc/$$/cmdline';
print <f>;
close(f);
Try that!
 
Old 01-07-2010, 11:43 PM   #7
ashok.g
Member
 
Registered: Dec 2009
Location: Hyderabad,India
Distribution: RHEl AS 4
Posts: 215

Original Poster
Rep: Reputation: 32
Quote:
Originally Posted by bartonski View Post
For Package.pl to be able to see the entire command line, it's going to have to make a call back to the shell. The shell has a variable '$COMP_LINE' contains the entire command line, but it's not populated by default... I didn't have time to read the entire section in the Bash man pages about this, but I know that it's there.
How can I invoke $COMP_LINE correctly in perl?

Hi bartonski and smeezekitty
By using the virtual file /proc/$$/cmdline, I am not able to get the specific command line arguments like "perl","-w", etc..,. Rather I am getting the total command line arguments as entire string. I tried as below:
Code:
#!usr/bin/perl
use strict;
use warnings;
open F, "/proc/$$/cmdline";
my @a=split "", <F>;
print @a,"\n";
close F;
How can I get the specific command for example "-w".



Thanks for your replies.
 
Old 01-08-2010, 11:39 AM   #8
bartonski
Member
 
Registered: Jul 2006
Location: Louisville, KY
Distribution: Fedora 12, Slackware, Debian, Ubuntu Karmic, FreeBSD 7.1
Posts: 443
Blog Entries: 1

Rep: Reputation: 48
Quote:
Originally Posted by ashok.g View Post
How can I invoke $COMP_LINE correctly in perl?

Hi bartonski and smeezekitty
By using the virtual file /proc/$$/cmdline, I am not able to get the specific command line arguments like "perl","-w", etc..,. Rather I am getting the total command line arguments as entire string. I tried as below:
Code:
#!usr/bin/perl
use strict;
use warnings;
open F, "/proc/$$/cmdline";
my @a=split "", <F>;
print @a,"\n";
close F;
How can I get the specific command for example "-w".



Thanks for your replies.
I ran smeezekitty's code, and /proc/$$/cmdline does in fact contain the '-w'. Smeezekitty's code splits the file into individual characters. If you want to see it by words, you have to use ascii 0 as the delimiter.

Code:
> cat /tmp/asdf.pl
#!usr/bin/perl
use strict;
use warnings;
open F, "/proc/$$/cmdline";
my @a=split "\000", <F>;
print "@a\n";
close F;

> perl -w /tmp/asdf.pl asdf asdf sadf sadf
perl -w /tmp/asdf.pl asdf asdf sadf sadf
 
Old 01-08-2010, 11:59 AM   #9
GooseYArd
Member
 
Registered: Jul 2009
Location: Reston, VA
Distribution: Slackware, Ubuntu, RHEL
Posts: 183

Rep: Reputation: 46
Quote:
Originally Posted by ashok.g View Post
How can I get the specific command for example "-w".
Why would you want to? If you're trying to detect whether perl is running -w so you can modify your own warnings behavior, you should just have your perl script accept -w as well.
 
0 members found this post helpful.
Old 01-08-2010, 12:30 PM   #10
bartonski
Member
 
Registered: Jul 2006
Location: Louisville, KY
Distribution: Fedora 12, Slackware, Debian, Ubuntu Karmic, FreeBSD 7.1
Posts: 443
Blog Entries: 1

Rep: Reputation: 48
Quote:
Originally Posted by GooseYArd View Post
Why would you want to? If you're trying to detect whether perl is running -w so you can modify your own warnings behavior, you should just have your perl script accept -w as well.
In general, I have to agree. If your perl script needs to resort to tricks like this, you probably need to revisit the design of your program. If you can't see a way around this on your own, you might also want to talk to someone about the design its self.
 
0 members found this post helpful.
Old 01-08-2010, 02:25 PM   #11
Telemachos
Member
 
Registered: May 2007
Distribution: Debian
Posts: 754

Rep: Reputation: 60
The -w is a flag not an argument. The Perl interpreter takes that and modifies execution accordingly (it turns on warnings), but the -w is not supposed to end up in @ARGV.

To jump ahead a little bit, can you tell us more about what you are really trying to do? If your goal is to be able to write command-line scripts with flags, Perl has lots of good modules to help you do that. Take a look at GetOpt::Std or Getopt::Long.
 
Old 01-08-2010, 02:58 PM   #12
MBybee
Member
 
Registered: Jan 2009
Location: wherever I can make a living
Distribution: OpenBSD / Debian / Ubuntu / Win7 / OpenVMS
Posts: 440

Rep: Reputation: 57
Quote:
Originally Posted by Telemachos View Post
The -w is a flag not an argument. The Perl interpreter takes that and modifies execution accordingly (it turns on warnings), but the -w is not supposed to end up in @ARGV.

To jump ahead a little bit, can you tell us more about what you are really trying to do? If your goal is to be able to write command-line scripts with flags, Perl has lots of good modules to help you do that. Take a look at GetOpt::Std or Getopt::Long.
Seconded - GetOpt is the right way to handle complex args.
To get the number of args just run $#ARGV, btw.
 
Old 01-08-2010, 04:25 PM   #13
GooseYArd
Member
 
Registered: Jul 2009
Location: Reston, VA
Distribution: Slackware, Ubuntu, RHEL
Posts: 183

Rep: Reputation: 46
Quote:
Originally Posted by MBybee View Post
Seconded - GetOpt is the right way to handle complex args.
To get the number of args just run $#ARGV, btw.
not quite- that'll be the number of args - 1, since ARGV[0] is the first argument (unlike C) You want scalar(@ARGV)
 
Old 01-08-2010, 04:52 PM   #14
rweaver
Senior Member
 
Registered: Dec 2008
Location: Louisville, OH
Distribution: Debian, CentOS, Slackware, RHEL, Gentoo
Posts: 1,833

Rep: Reputation: 167Reputation: 167
Another thing I'd point out is... you should really be specifying the commandline uses in the script itself--

Code:
use strict;
use warnings;
There is really no time you don't want those on. $0 will return perl and it's full path and as someone said earlier $#ARGV+1 will return the number of *arguments*, but *perl* flags aren't arguements. I don't recall a way to grab what perl flags are in use however.

You can see an example of this like such:

Code:
perl -e 'print $0 . " has " . (($#ARGV)+1) . " args.\n"'
test.pl:
Code:
#!/usr/bin/perl
print $0 . " has " . (($#ARGV)+1) . " args.\n"
Code:
core:~/test/test22$ perl -e 'print $0 . " has " . (($#ARGV)+1) . " args.\n"' 1 2 3
-e has 3 args.
core:~/test/test22$ ./test.pl asd as a
./test.pl has 3 args.
core:~/test/test22$ perl -w test.pl asd as a
test.pl has 3 args.

Last edited by rweaver; 01-11-2010 at 01:15 PM.
 
Old 01-08-2010, 04:53 PM   #15
MBybee
Member
 
Registered: Jan 2009
Location: wherever I can make a living
Distribution: OpenBSD / Debian / Ubuntu / Win7 / OpenVMS
Posts: 440

Rep: Reputation: 57
Quote:
Originally Posted by GooseYArd View Post
not quite- that'll be the number of args - 1, since ARGV[0] is the first argument (unlike C) You want scalar(@ARGV)
Sure - that's true that it gives you the size of an array counting from 0. Both give you the size, though they give you a different value Best part of perl is that there are many ways to shoot off your foot. I happen to prefer arrays 0 based, so that I can walk through it like this:

for( $val= 0; $val <= $#ARRAY; $val++ ){
}
Which is just a C habit.

However, it's all about preference, and both will work. Yay Perl
 
  


Reply

Tags
arguments, perl



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
call perl script through another perl script with arguments nanda22 Linux - Newbie 21 07-21-2009 12:18 AM
Problem with passing arguments in Perl bahadur Programming 1 05-30-2005 01:47 AM
perl arguments zaken Programming 1 02-27-2005 11:19 AM
command arguments in perl djgerbavore Programming 1 12-30-2004 08:06 AM
Perl: Getting a script to accept arguments JStew Programming 10 03-10-2003 06:56 AM

LinuxQuestions.org > Forums > Non-*NIX Forums > Programming

All times are GMT -5. The time now is 05:58 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration