Here an example of how you can check the input argument:
Code:
$ echo "-4" | perl -nE 'm/^-(\d+)$/ and say $1 or die qq|Bad argument\n|'
4
$ echo "+-4" | perl -nE 'm/^-(\d+)$/ and say $1 or die qq|Bad argument\n|'
Bad argument
$ echo "-42354" | perl -nE 'm/^-(\d+)$/ and say $1 or die qq|Bad argument\n|'
42354
$ echo "42354" | perl -nE 'm/^-(\d+)$/ and say $1 or die qq|Bad argument\n|'
Bad argument
Hi List,
Is it possible to pass one argument to a shell program
eg) there is a shell program abc which takes one arguments
abc one
Due to some reasons I pass
abc one two
Now one,two must be considered as "one" argument to the shell programs. Any suggestions,hints are welcome.
... (3 Replies)
Can someone help me to understand this part of code?
/bin/nawk -f awkfile file1 file2
I know awkfile is the one with awk script.
file1 is source file that needs to be processed.
What is file2 two?
Thanks for your help! (4 Replies)
In DDD debugger, where to set the the arguments for main program?
For example: ./myExe "argv1" "argv2" -> where to set "argv1" & "argv2" ?
Thanks! (2 Replies)
I have a shell script that is attempting to call a c program.
I call the c program with ./dictool
dictool accepts arguments at runtime. It works by prompting the user for various commands, acting on those commands, spitting out an output, and then prompting for more commands.
My question is,... (1 Reply)
I have the following piece of code. Currently the command line arguments are passed as shown below using the "= "sign. I capture the name of the argument, for example vmod and it's corresponding user parameter which is jcdint-z30.cmd.
./raytrac vmod=jcdint-z30.cmd srFile=jcdint.sr
Now I want... (12 Replies)
Hello,
The arguments are strings. In my code I need them to be a different type, I do the cast but it is not feasible ...
Have you any idea?
Thank you (8 Replies)
I want to write a C++ program that uses a class to do some calculations.
I pass arguments to the program, some of which are used to set up class members. A class function will then perform the necessary calculations.
I am wondering how I should pass the arguments from the program to set the... (2 Replies)
Dear Users,
I have installed a standalone program to do multiple sequence alignment which takes user parameters to run the program. I have multiple sequence files and want to automate this process through a bash script. I have tried to write a small bash code but its throwing errors.
Kindly... (13 Replies)
#!/bin/awk -f
BEGIN {
FS=":";
}
{
if ( $7 == "" ) {
print $1 ": no password!";
}
}
I want to execute this program for a particular user to check for his password from the file /etc/passwd (as the input file) and the user details to be given... (1 Reply)
Perl::Critic::Policy::ErrorHandling::RequireCarping(3) User Contributed Perl Documentation Perl::Critic::Policy::ErrorHandling::RequireCarping(3)NAME
Perl::Critic::Policy::ErrorHandling::RequireCarping - Use functions from Carp instead of "warn" or "die".
AFFILIATION
This Policy is part of the core Perl::Critic distribution.
DESCRIPTION
The "die" and "warn" functions both report the file and line number where the exception occurred. But if someone else is using your
subroutine, they usually don't care where your code blew up. Instead, they want to know where their code invoked the subroutine. The Carp
module provides alternative methods that report the exception from the caller's file and line number.
By default, this policy will not complain about "die" or "warn", if it can determine that the message will always result in a terminal
newline. Since perl suppresses file names and line numbers in this situation, it is assumed that no stack traces are desired either and
none of the Carp functions are necessary.
die "oops" if $explosion; #not ok
warn "Where? Where?!" if $tiger; #not ok
open my $mouth, '<', 'food'
or die 'of starvation'; #not ok
if (! $dentist_appointment) {
warn "You have bad breath!
"; #ok
}
die "$clock not set.
" if $no_time; #ok
my $message = "$clock not set.
";
die $message if $no_time; #not ok, not obvious
CONFIGURATION
By default, this policy allows uses of "die" and "warn" ending in an explicit newline. If you give this policy an
"allow_messages_ending_with_newlines" option in your .perlcriticrc with a false value, then this policy will prohibit such uses.
[ErrorHandling::RequireCarping]
allow_messages_ending_with_newlines = 0
If you give this policy an "allow_in_main_unless_in_subroutine" option in your .perlcriticrc with a true value, then this policy will allow
"die" and "warn" in name space main:: unless they appear in a subroutine, even if they do not end in an explicit newline.
[ErrorHandling::RequireCarping]
allow_in_main_unless_in_subroutine = 1
BUGS
Should allow "die" when it is obvious that the "message" is a reference.
SEE ALSO
Carp::Always
AUTHOR
Jeffrey Ryan Thalhammer <jeff@imaginative-software.com>
COPYRIGHT
Copyright (c) 2005-2011 Imaginative Software Systems. All rights reserved.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. The full text of this license
can be found in the LICENSE file included with this module.
perl v5.16.3 2014-06-09 Perl::Critic::Policy::ErrorHandling::RequireCarping(3)