01-29-2013
I see you addressed the first and last point but not nrs. 2 and 3. Also, $label does now get initialized from "check_parameters" after the case statement for the fun[123] function calls
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
All,
I have a sh script of the following tune:
function a () { #functionality.. }
function b () { #functionnlity.. }
function check () { # this function checks for env and if all fine call build }
function usage () { #sh usage details }
function build () { #calls either a or b or... (5 Replies)
Discussion started by: vino
5 Replies
2. Shell Programming and Scripting
hi
could anybody please suggest me how to put a function memory for particular user.
say i am a user rao. want have a function foo in memory .
i have done this .typed the function function in the shell it worked for the session.but next time i do login its not there .
i can i have a... (6 Replies)
Discussion started by: Raom
6 Replies
3. Shell Programming and Scripting
Hi I have 2 files a.c and a.bak where I changed long to int using awk script.
I want to get the list of functions whose parameters got modified
for eg: fun ( long a, long b ) might be changed to fun ( int a, int b ) (1 Reply)
Discussion started by: Sivaswami
1 Replies
4. Shell Programming and Scripting
Hello,
I'm trying to run a program on a directory (traverse sub dirs too) through my csh script. Arrays support in CSH is appalling, something like associative arrays would have helped me do this so much easier.
Anyway, I want to hold some details extracted from the program and then at the... (0 Replies)
Discussion started by: ragabonds
0 Replies
5. Shell Programming and Scripting
Hi,
Please help me with the below situation where I have to handle the parameters passed to a function in a unique way.
Below is the code, which I am trying to execute. I basically want to pass the parameter to a function, where I am trying to get user input into array(s). I want to name... (7 Replies)
Discussion started by: bharath.gct
7 Replies
6. Shell Programming and Scripting
Hi
I would like to place in one line output from two functions. Both functions return text with print cmd.
When I place above code in script it will place them in series.
e.g.
1 #/bin/ksh
2
3 function1()
4 {
5 print "My name is"
6 ... (3 Replies)
Discussion started by: presul
3 Replies
7. Shell Programming and Scripting
Hi! I've a C file which consist of many function definitions with numbers at the beginning as shown below..
10 void search()
11 {
12 /*body
14 *
15 *
17 *
18 *
40 *
42 *
60 }
90 void func_name()
95 {
99 /*body
100 *
105 *
111 * (7 Replies)
Discussion started by: abk07
7 Replies
8. Shell Programming and Scripting
Hi ,
I have a script which is using a text file as I/P.
I want a code where it reads n lines from this file and pass the parameters to a function and now this script should run in such a way where a function can be called in parallel with different parameters. Please find below my script, it... (1 Reply)
Discussion started by: Ravindra Swan
1 Replies
9. Shell Programming and Scripting
Hi,
I am a beginner in python programming. In my python script have a main function which calls several other functions. The main function gets its input by reading lines from a input text file. I call the main function for every line in input text file through a loop.
def main(line):
var1... (6 Replies)
Discussion started by: ctrld
6 Replies
LEARN ABOUT DEBIAN
perl::critic::policy::controlstructures::prohibitunreachablecode
Perl::Critic::Policy::ControlStructures::ProhibitUnreachUserCContributed PerlPerl::Critic::Policy::ControlStructures::ProhibitUnreachableCode(3pm)
NAME
Perl::Critic::Policy::ControlStructures::ProhibitUnreachableCode - Don't write code after an unconditional "die, exit, or next".
AFFILIATION
This Policy is part of the core Perl::Critic distribution.
DESCRIPTION
This policy prohibits code following a statement which unconditionally alters the program flow. This includes calls to "exit", "die",
"return", "next", "last" and "goto". Due to common usage, "croak" and "confess" from Carp are also included.
Code is reachable if any of the following conditions are true:
o Flow-altering statement has a conditional attached to it
o Statement is on the right side of an operator "&&", "||", "//", "and", "or", or "err".
o Code is prefixed with a label (can potentially be reached via "goto")
o Code is a subroutine
EXAMPLES
# not ok
exit;
print "123
";
# ok
exit if !$xyz;
print "123
";
# not ok
for ( 1 .. 10 ) {
next;
print 1;
}
# ok
for ( 1 .. 10 ) {
next if $_ == 5;
print 1;
}
# not ok
sub foo {
my $bar = shift;
return;
print 1;
}
# ok
sub foo {
my $bar = shift;
return if $bar->baz();
print 1;
}
# not ok
die;
print "123
";
# ok
die;
LABEL: print "123
";
# not ok
croak;
do_something();
# ok
croak;
sub do_something {}
CONFIGURATION
This Policy is not configurable except for the standard options.
SEE ALSO
Perl::Critic::Policy::ControlStructures::ProhibitPostfixControls
AUTHOR
Peter Guzis <pguzis@cpan.org>
COPYRIGHT
Copyright (c) 2006-2011 Peter Guzis. 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.14.2 2012-06-0Perl::Critic::Policy::ControlStructures::ProhibitUnreachableCode(3pm)