LinuxQuestions.org - [SOLVED] How to get the total arguments in perl??

- Programming (https://www.linuxquestions.org/questions/programming-9/)

- - How to get the total arguments in perl?? (https://www.linuxquestions.org/questions/programming-9/how-to-get-the-total-arguments-in-perl-780446/)

Quote:

Originally Posted by rweaver (Post 3819507)

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.

Hallelujah, Brother.

I didn't really learn that this was the right way to do things until I started working in a mixed Unix/Windows environment:

I used to run perl scripts using this shebang line.

Code:

#! /usr/bin/perl -w

That won't work under Windows.

(What's worse is when someone opens one of your perl files in a windows text editor... then saves it without makeing any changes... except for the nice little ^M characters littered throughout the code. This will mess up the shebang line because /usr/bin/perl is not the same as /usr/bin/perl^M... meaning that the shebang line won't work under Unix, either).

Quote:

Originally Posted by bartonski (Post 3819059)

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.plasdfasdfsadfsadf

Please observe that I used print @a,"\n"; instead of print @a,"\n";.
Why this is happening?

Quote:

Originally Posted by ashok.g (Post 3822141)

Please observe that I used print @a,"\n"; instead of print @a,"\n";.
Why this is happening?

What "this" ?

Quote:

Originally Posted by ashok.g (Post 3822141)

Please observe that I used print @a,"\n"; instead of print @a,"\n";.
Why this is happening?

I believe you mean print @a, "\n"; instead of print "@a\n";.

If you interpolate an array in double quotes and print it, you get each item separated by a space. If, however, you print the array unquoted, you get all the items concatenated together without any separation of any kind.

Code:

#!/usr/bin/env perl

use strict;

use warnings;



my @stuff = qw/foo bar bizz buzz fizzbuzz/;



print "With quotes:\n";

print "\t@stuff\n";



print "Without quotes:\n";

print "\t", @stuff, "\n";

Output:

Code:

telemachus ~ $ perl array_print

With quotes:

        foo bar bizz buzz fizzbuzz

Without quotes:

        foobarbizzbuzzfizzbuzz

Note that the behavior of interpolated arrays (space separated) can be adjusted by tinkering with the $" built-in variable.

Quote:

Originally Posted by Telemachos (Post 3822310)

Code:

#!/usr/bin/env perl

use strict;

use warnings;



my @stuff = qw/foo bar bizz buzz fizzbuzz/;



print "With quotes:\n";

print "\t@stuff\n";



print "Without quotes:\n";

print "\t", @stuff, "\n";

Output:

Code:

telemachus ~ $ perl array_print

With quotes:

        foo bar bizz buzz fizzbuzz

Without quotes:

        foobarbizzbuzzfizzbuzz

Note that the behavior of interpolated arrays (space separated) can be adjusted by tinkering with the $" built-in variable.

Such answers leave the OP no chance to learn to ask questions correctly in the first place.

Quote:

Originally Posted by Sergei Steshenko (Post 3822325)

Such answers leave the OP no chance to learn to ask questions correctly in the first place.

That is your opinion, and you have every right to it. In my opinion, your style of answer ("Here are the docs. Read them. If you don't understand something, write here, explaining the first word you don't understand and why...") makes people ask elsewhere (or give up).

I will continue to answer in my style. You can continue to disagree with my choices. Such is life.

Quote:

Originally Posted by Telemachos (Post 3822964)

That is your opinion, and you have every right to it. In my opinion, your style of answer ("Here are the docs. Read them. If you don't understand something, write here, explaining the first word you don't understand and why...") makes people ask elsewhere (or give up).

I will continue to answer in my style. You can continue to disagree with my choices. Such is life.

They'd better give up - otherwise their job has to be done by others.

As someone else wrote in this forum - instead of learning nowadays "Internet forum learning" or something like this has become immensely popular. I.e. instead of making an effort to read and understand people just ask questions in forums without making an effort first.

Unfortunately, I too often had to work with people who never bothered to read the documentation on tools they were systematically/repeatedly using.

It was a disaster, i.e. they didn't understand how the tools were working/what they were doing, they just new command line format for certain tasks they were routinely performing. They couldn't make even a minimal modification of the command lines when needed (i.e. all they could was, say, replacing file names on command lines), they couldn't analyze and correct mistakes they made (and we all make mistakes) - exactly because they didn't understand what they and the tools were doing.

Kind of "command line monkeys" if you wish - similar to "coding monkeys".

As you said, such is life. I.e. the more you do the job of others, the more the others take it for granted.

Quote:

Originally Posted by Sergei Steshenko (Post 3823349)

They'd better give up - otherwise their job has to be done by others.

<snip>

As you said, such is life. I.e. the more you do the job of others, the more the others take it for granted.

This is a reasonable response, so I will try to explain why I disagree. I agree that if people use forums only to get the answer, they won't ever learn.

However, my hope is that if I give more explanation and people read what I write and think about it, they will learn. I also generally post links to fuller documentation or articles or mention books. If someone posts question after question about very basic things and doesn't show any increase in knowledge, I stop posting answers. But I don't mind writing fuller answers at first.

Perl's documentation is excellent, but it can be overwhelming for someone new to the language or new to programming. I remember how it felt for me at first. Everything was in there, but (1) I couldn't always find things and (2) sometimes the explanations went way over my head.

Anyhow, that's why I often write fuller answers.