Sponsored Content
Full Discussion: Looping through the argument
Top Forums Shell Programming and Scripting Looping through the argument Post 302326875 by dwgi32 on Friday 19th of June 2009 05:15:39 AM
Old 06-19-2009
Looping through the argument

Hi,

I would like to perform a loop through the passing in argument, is there any method.

I.e

command> my_script a b c d

my_script
----------
for i in $#
echo $i
done
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

help on looping using if/for or while

Hello, where can I get usefull information on the use of looping with for , if and while with extensive examples. Also use of variables in scripts (1 Reply)
Discussion started by: sam4now
1 Replies

2. Shell Programming and Scripting

help with looping

vesselNames values: xxx yyy zzz vesselPlanned values: xxx zzz zzz zzz OIFS="" OIFS=$IFS IFS="\n" (2 Replies)
Discussion started by: finalight
2 Replies

3. UNIX for Dummies Questions & Answers

How to find the last argument in a argument line?

How to find the last argument in a argument line? (4 Replies)
Discussion started by: nehagupta2008
4 Replies

4. Shell Programming and Scripting

Looping

Hi, Now I have written a script which sorts the records in the file and splits them according to some condition. Now, I need to modify the script so that it reads all the files one after the other and does the sorting & splitting. Pls help me in reading all the files in a directory and... (8 Replies)
Discussion started by: Sunitha_edi82
8 Replies

5. Shell Programming and Scripting

get positive number n as argument script must calculate the factorial of its argument

Can someone please help me with this SHELL script? I need to create a script that gets a positive number n as an argument. The script must calculate the factorial of its argument. In other words, it must calculate n!=1x2x3x...xn. Note that 0!=1. Here is a start but I have no clue how to... (3 Replies)
Discussion started by: I-1
3 Replies

6. Shell Programming and Scripting

Cannot compare argument in if statement in csh/grep command if argument starts with “-“

If ($argv == “-debug”) then Echo “in loop” Endif But this is not working. If I modify this code and remove “-“, then it works. Similarly I am getting problem using grep command also Grep “-debug” Filename Can someone please help me on how to resolve these... (1 Reply)
Discussion started by: sarbjit
1 Replies

7. Shell Programming and Scripting

Looping

Hi evryone i need a help . i have a file xcv.the content is : accelerate i want a script which will run 1000 times in loop and changing the value to accelerate to acceler in 1st loop and in 2nd loop it will be again accelerate and so on . (6 Replies)
Discussion started by: Aditya.Gurgaon
6 Replies

8. Shell Programming and Scripting

Make script that run with argument if not run from configuration file argument

Hello, Is there any method thorugh which script can take argument if pass otherwise if argument doesn't pass then it takes the argument from the configuration file i.e I am workiing on a script which will run through crontab and the script will chekout the code ,zip and copy to the... (3 Replies)
Discussion started by: rohit22hamirpur
3 Replies

9. UNIX for Advanced & Expert Users

Error:--test: argument expected--Even though i give an argument.

Hi All, I am running the script VBoxManage list vms |sed 's/"//g' | cut -d " " -f1 > har1out.mytxt result=`cat har1out.mytxt | grep $1' echo $result echo $1 { if then echo pass else echo fail fi (2 Replies)
Discussion started by: harsha85
2 Replies

10. Shell Programming and Scripting

Looping

Hey guys, so I am trying to do a loop script that will go through each folder (no gui so just each domain has a folder) and grab out the databases being used on that domain. I know I would use mysql -e "show databases where not 'information_schema';" once in each directory to pull the actual... (3 Replies)
Discussion started by: dough
3 Replies
MooseX::Getopt(3pm)					User Contributed Perl Documentation				       MooseX::Getopt(3pm)

NAME
MooseX::Getopt - A Moose role for processing command line options VERSION
version 0.59 SYNOPSIS
## In your class package My::App; use Moose; with 'MooseX::Getopt'; has 'out' => (is => 'rw', isa => 'Str', required => 1); has 'in' => (is => 'rw', isa => 'Str', required => 1); # ... rest of the class here ## in your script #!/usr/bin/perl use My::App; my $app = My::App->new_with_options(); # ... rest of the script here ## on the command line % perl my_app_script.pl -in file.input -out file.dump DESCRIPTION
This is a role which provides an alternate constructor for creating objects using parameters passed in from the command line. METHODS
"new_with_options (%params)" This method will take a set of default %params and then collect parameters from the command line (possibly overriding those in %params) and then return a newly constructed object. The special parameter "argv", if specified should point to an array reference with an array to use instead of @ARGV. If "GetOptions" in Getopt::Long fails (due to invalid arguments), "new_with_options" will throw an exception. If Getopt::Long::Descriptive is installed and any of the following command line parameters are passed, the program will exit with usage information (and the option's state will be stored in the help_flag attribute). You can add descriptions for each option by including a documentation option for each attribute to document. -? --? -h --help --usage If you have Getopt::Long::Descriptive the "usage" parameter is also passed to "new" as the usage option. "ARGV" This accessor contains a reference to a copy of the @ARGV array as it originally existed at the time of "new_with_options". "extra_argv" This accessor contains an arrayref of leftover @ARGV elements that Getopt::Long did not parse. Note that the real @ARGV is left untouched. Important: By default, Getopt::Long will reject unrecognized options (that is, options that do not correspond with attributes using the Getopt trait). To disable this, and allow options to also be saved in "extra_argv" (for example to pass along to another class's "new_with_options"), you can either enable the "pass_through" option of Getopt::Long for your class: "use Getopt::Long qw(:config pass_through);" or specify a value for MooseX::Getopt::GLD's "getopt_conf" parameter. "usage" This accessor contains the Getopt::Long::Descriptive::Usage object (if Getopt::Long::Descriptive is used). "help_flag" This accessor contains the boolean state of the --help, --usage and --? options (true if any of these options were passed on the command line). "print_usage_text" This method is called internally when the "help_flag" state is true. It prints the text from the "usage" object (see above) to "stdout" and then the program terminates normally. You can apply a method modification (see Moose::Manual::MethodModifiers) if different behaviour is desired, for example to include additional text. "meta" This returns the role meta object. "process_argv (%params)" This does most of the work of "new_with_options", analyzing the parameters and "argv", except for actually calling the constructor. It returns a MooseX::Getopt::ProcessedArgv object. "new_with_options" uses this method internally, so modifying this method via subclasses/roles will affect "new_with_options". This module attempts to DWIM as much as possible with the command line parameters by introspecting your class's attributes. It will use the name of your attribute as the command line option, and if there is a type constraint defined, it will configure Getopt::Long to handle the option accordingly. You can use the trait MooseX::Getopt::Meta::Attribute::Trait or the attribute metaclass MooseX::Getopt::Meta::Attribute to get non-default command-line option names and aliases. You can use the trait MooseX::Getopt::Meta::Attribute::Trait::NoGetopt or the attribute metaclass MooseX::Getopt::Meta::Attribute::NoGetopt to have "MooseX::Getopt" ignore your attribute in the command-line options. By default, attributes which start with an underscore are not given command-line argument support, unless the attribute's metaclass is set to MooseX::Getopt::Meta::Attribute. If you don't want your accessors to have the leading underscore in their name, you can do this: # for read/write attributes has '_foo' => (accessor => 'foo', ...); # or for read-only attributes has '_bar' => (reader => 'bar', ...); This will mean that Getopt will not handle a --foo parameter, but your code can still call the "foo" method. If your class also uses a configfile-loading role based on MooseX::ConfigFromFile, such as MooseX::SimpleConfig, MooseX::Getopt's "new_with_options" will load the configfile specified by the "--configfile" option (or the default you've given for the configfile attribute) for you. Options specified in multiple places follow the following precedence order: command-line overrides configfile, which overrides explicit new_with_options parameters. Supported Type Constraints Bool A Bool type constraint is set up as a boolean option with Getopt::Long. So that this attribute description: has 'verbose' => (is => 'rw', isa => 'Bool'); would translate into "verbose!" as a Getopt::Long option descriptor, which would enable the following command line options: % my_script.pl --verbose % my_script.pl --noverbose Int, Float, Str These type constraints are set up as properly typed options with Getopt::Long, using the "=i", "=f" and "=s" modifiers as appropriate. ArrayRef An ArrayRef type constraint is set up as a multiple value option in Getopt::Long. So that this attribute description: has 'include' => ( is => 'rw', isa => 'ArrayRef', default => sub { [] } ); would translate into "includes=s@" as a Getopt::Long option descriptor, which would enable the following command line options: % my_script.pl --include /usr/lib --include /usr/local/lib HashRef A HashRef type constraint is set up as a hash value option in Getopt::Long. So that this attribute description: has 'define' => ( is => 'rw', isa => 'HashRef', default => sub { {} } ); would translate into "define=s%" as a Getopt::Long option descriptor, which would enable the following command line options: % my_script.pl --define os=linux --define vendor=debian Custom Type Constraints It is possible to create custom type constraint to option spec mappings if you need them. The process is fairly simple (but a little verbose maybe). First you create a custom subtype, like so: subtype 'ArrayOfInts' => as 'ArrayRef' => where { scalar (grep { looks_like_number($_) } @$_) }; Then you register the mapping, like so: MooseX::Getopt::OptionTypeMap->add_option_type_to_map( 'ArrayOfInts' => '=i@' ); Now any attribute declarations using this type constraint will get the custom option spec. So that, this: has 'nums' => ( is => 'ro', isa => 'ArrayOfInts', default => sub { [0] } ); Will translate to the following on the command line: % my_script.pl --nums 5 --nums 88 --nums 199 This example is fairly trivial, but more complex validations are easily possible with a little creativity. The trick is balancing the type constraint validations with the Getopt::Long validations. Better examples are certainly welcome :) Inferred Type Constraints If you define a custom subtype which is a subtype of one of the standard "Supported Type Constraints" above, and do not explicitly provide custom support as in "Custom Type Constraints" above, MooseX::Getopt will treat it like the parent type for Getopt purposes. For example, if you had the same custom "ArrayOfInts" subtype from the examples above, but did not add a new custom option type for it to the "OptionTypeMap", it would be treated just like a normal "ArrayRef" type for Getopt purposes (that is, "=s@"). More Customization Options See "Configuring Getopt::Long" in Getopt::Long for many other customizations you can make to how options are parsed. Simply "use Getopt::Long qw(:config other_options...)" in your class to set these. SEE ALSO
MooseX::Getopt::Usage, an extension to generate man pages, with colour AUTHOR
Stevan Little <stevan@iinteractive.com> COPYRIGHT AND LICENSE
This software is copyright (c) 2007 by Infinity Interactive, Inc. This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself. CONTRIBUTORS
o Brandon L Black <blblack@gmail.com> o Chris Prather <chris@prather.org> o Dagfinn Ilmari Mannsaaker <ilmari@ilmari.org> o Damien Krotkine <dkrotkine@weborama.com> o Devin Austin <devin@devin-laptop.(none)> o Drew Taylor <drew@drewtaylor.com> o Florian Ragwitz <rafl@debian.org> o Gordon Irving <goraxe@goraxe.me.uk> o Hans Dieter Pearcey <hdp@weftsoar.net> o Hinrik Oern Sigur`sson <hinrik.sig@gmail.com> o Jesse Luehrs <doy@tozt.net> o John Goulah <jgoulah@cpan.org> o Jonathan Swartz <swartz@pobox.com> o Justin Hunter <justin.d.hunter@gmail.com> o Karen Etheridge <ether@cpan.org> o Nelo Onyiah <nelo.onyiah@gmail.com> o Ricardo SIGNES <rjbs@cpan.org> o Ryan D Johnson <ryan@innerfence.com> o Shlomi Fish <shlomif@iglu.org.il> o Stevan Little <stevan.little@iinteractive.com> o Todd Hepler <thepler@employees.org> o Tomas Doran <bobtfish@bobtfish.net> o Yuval Kogman <nothingmuch@woobling.org> o AEvar Arnfjoer` Bjarmason <avarab@gmail.com> perl v5.18.2 2013-11-30 MooseX::Getopt(3pm)
All times are GMT -4. The time now is 03:13 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy