Sponsored Content
Top Forums Shell Programming and Scripting BASH: Factorial using FOR loop not working Post 302437591 by DeCoTwc on Thursday 15th of July 2010 12:41:26 PM
Old 07-15-2010
You were really close. For arithmetic, use parentheses, not brackets:

Code:
(12:40:19\[D@DeCoBox15)
[~]$ cat fact
#!/bin/bash
# using one command line parameter

factorial=1
for (( number = 1; number <= $1 ; number++ ))
do
factorial=$(($factorial * $number))
done
echo The factorial of $1 is $factorial

(12:40:21\[D@DeCoBox15)
[~]$ bash fact 12
The factorial of 12 is 479001600

 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

If then else loop not working

If then else segment of below code is not working. For each filename code is displaying output for if part as well as else part. Please help its urgent. for usercusttop in `echo ${filename}|sort|uniq|cut -c 1-${actualwordcount}` do ... (2 Replies)
Discussion started by: findprakash
2 Replies

2. UNIX for Advanced & Expert Users

If loop is not working

The following piece of code is not running because it is fails to go inside the if condition. i want to create a directory if there is no directory in the input path. i am using Linux, by CENT. Please help. echo " Enter the path where you u want to extract the tar" read EXTRACT_PATH ls -ld... (12 Replies)
Discussion started by: toanilsharma1
12 Replies

3. Shell Programming and Scripting

bash and ksh: variable lost in loop in bash?

Hi, I use AIX (ksh) and Linux (bash) servers. I'm trying to do scripts to will run in both ksh and bash, and most of the time it works. But this time I don't get it in bash (I'm more familar in ksh). The goal of my script if to read a "config file" (like "ini" file), and make various report.... (2 Replies)
Discussion started by: estienne
2 Replies

4. Shell Programming and Scripting

if loop not working in BASH shell

i have this code for a simple if loop: #!/bin/bash array="1 2 3 4 5" array2="5 6 7 8 9" if } -gt ${array} ]; then echo "${array2} is greater than ${array}!!" fi the error is ./script8: line 9: [: too many arguments ./script8: line 9: [: too many arguments ./script8: line 9: [:... (10 Replies)
Discussion started by: npatwardhan
10 Replies

5. UNIX for Dummies Questions & Answers

Anyone know?: How the 'for'-loop could stop working in interactive bash shell?!

It is happening with my sessions already second time: a 'for'-loop for some reason stop to work as expected. That means or it is looping without exitting, or it is not loop even once. Here example of my try when it is not processing even one loop. You can see, I start new subshell and... (14 Replies)
Discussion started by: alex_5161
14 Replies

6. Shell Programming and Scripting

Using variables created sequentially in a loop while still inside of the loop [bash]

I'm trying to understand if it's possible to create a set of variables that are numbered based on another variable (using eval) in a loop, and then call on it before the loop ends. As an example I've written a script called question (The fist command is to show what is the contents of the... (2 Replies)
Discussion started by: DeCoTwc
2 Replies

7. Shell Programming and Scripting

BASH loop inside a loop question

Hi all Sorry for the basic question, but i am writing a shell script to get around a slightly flaky binary that ships with one of our servers. This particular utility randomly generates the correct information and could work first time or may work on the 12th or 100th attempt etc !.... (4 Replies)
Discussion started by: rethink
4 Replies

8. Shell Programming and Scripting

Factorial of any number using functions

how to write the code for factorial of any number using functions and arguments????? (7 Replies)
Discussion started by: kullu
7 Replies

9. Shell Programming and Scripting

README: Factorial quick chart with sed & bc:

Hi all, While doing some checks I found a kind of interesting arithmetic factorial chart with sed, sharing this may be simple but thought to share, # n=20;for i in `seq $n`;do printf "`seq $i|xargs|sed 's/ /*/g'`= ";echo "`seq $i|xargs|sed 's/ /*/g'`"| bc;done 1= 1 1*2= 2 1*2*3= 6... (6 Replies)
Discussion started by: rveri
6 Replies

10. Shell Programming and Scripting

For-loop not working

Hello all, I would like to unzip some files with a for-loop. Is there anyone who could tell me how I should do this - in a correct way? for file in $(ls); do echo gzip -d < $file | tar xf -; done The problem is the pipe - I believe. But how could I do it? I need it for the command... (4 Replies)
Discussion started by: API
4 Replies
return(n)						       Tcl Built-In Commands							 return(n)

__________________________________________________________________________________________________________________________________________________

NAME
return - Return from a procedure, or set return code of a script SYNOPSIS
return ?result? return ?-code code? ?result? return ?option value ...? ?result? _________________________________________________________________ DESCRIPTION
In its simplest usage, the return command is used without options in the body of a procedure to immediately return control to the caller of the procedure. If a result argument is provided, its value becomes the result of the procedure passed back to the caller. If result is not specified then an empty string will be returned to the caller as the result of the procedure. The return command serves a similar function within script files that are evaluated by the source command. When source evaluates the con- tents of a file as a script, an invocation of the return command will cause script evaluation to immediately cease, and the value result (or an empty string) will be returned as the result of the source command. EXCEPTIONAL RETURN CODES
In addition to the result of a procedure, the return code of a procedure may also be set by return through use of the -code option. In the usual case where the -code option is not specified the procedure will return normally. However, the -code option may be used to generate an exceptional return from the procedure. Code may have any of the following values: ok (or 0) Normal return: same as if the option is omitted. The return code of the procedure is 0 (TCL_OK). error (1) Error return: the return code of the procedure is 1 (TCL_ERROR). The procedure command behaves in its calling context as if it were the command error result. See below for additional options. return (2) The return code of the procedure is 2 (TCL_RETURN). The procedure command behaves in its calling context as if it were the command return (with no arguments). break (3) The return code of the procedure is 3 (TCL_BREAK). The procedure command behaves in its calling context as if it were the command break. continue (4) The return code of the procedure is 4 (TCL_CONTINUE). The procedure command behaves in its calling context as if it were the command continue. value Value must be an integer; it will be returned as the return code for the current procedure. When a procedure wants to signal that it has received invalid arguments from its caller, it may use return -code error with result set to a suitable error message. Otherwise usage of the return -code option is mostly limited to procedures that implement a new control structure. The return -code command acts similarly within script files that are evaluated by the source command. During the evaluation of the con- tents of a file as a script by source, an invocation of the return -code code command will cause the return code of source to be code. RETURN OPTIONS
In addition to a result and a return code, evaluation of a command in Tcl also produces a dictionary of return options. In general usage, | all option value pairs given as arguments to return become entries in the return options dictionary, and any values at all are acceptable | except as noted below. The catch command may be used to capture all of this information -- the return code, the result, and the return | options dictionary -- that arise from evaluation of a script. As documented above, the -code entry in the return options dictionary receives special treatment by Tcl. There are other return options also recognized and treated specially by Tcl. They are: -errorcode list The -errorcode option receives special treatment only when the value of the -code option is TCL_ERROR. Then the list value is meant to be additional information about the error, presented as a Tcl list for further processing by programs. If no -errorcode option is provided to return when the -code error option is provided, Tcl will set the value of the -errorcode entry in the return options dictionary to the default value of NONE. The -errorcode return option will also be stored in the global variable errorCode. -errorinfo info The -errorinfo option receives special treatment only when the value of the -code option is TCL_ERROR. Then info is the initial stack trace, meant to provide to a human reader additional information about the context in which the error occurred. The stack trace will also be stored in the global variable errorInfo. If no -errorinfo option is provided to return when the -code error option is provided, Tcl will provide its own initial stack trace value in the entry for -errorinfo. Tcl's initial stack trace will include only the call to the procedure, and stack unwinding will append information about higher stack levels, but there will be no information about the context of the error within the procedure. Typically the info value is supplied from the value of -errorinfo in a return options dictionary captured by the catch command (or from the copy of that information stored in the global variable errorInfo). -level level The -level and -code options work together to set the return code to be returned by one of the commands currently being evaluated. | The level value must be a non-negative integer representing a number of levels on the call stack. It defines the number of levels | up the stack at which the return code of a command currently being evaluated should be code. If no -level option is provided, the | default value of level is 1, so that return sets the return code that the current procedure returns to its caller, 1 level up the | call stack. The mechanism by which these options work is described in more detail below. -options options The value options must be a valid dictionary. The entries of that dictionary are treated as additional option value pairs for the | return command. RETURN CODE HANDLING MECHANISMS
Return codes are used in Tcl to control program flow. A Tcl script is a sequence of Tcl commands. So long as each command evaluation returns a return code of TCL_OK, evaluation will continue to the next command in the script. Any exceptional return code (non-TCL_OK) returned by a command evaluation causes the flow on to the next command to be interrupted. Script evaluation ceases, and the exceptional return code from the command becomes the return code of the full script evaluation. This is the mechanism by which errors during script evaluation cause an interruption and unwinding of the call stack. It is also the mechanism by which commands like break, continue, and return cause script evaluation to terminate without evaluating all commands in sequence. Some of Tcl's built-in commands evaluate scripts as part of their functioning. These commands can make use of exceptional return codes to enable special features. For example, the built-in Tcl commands that provide loops -- such as while, for, and foreach -- evaluate a script that is the body of the loop. If evaluation of the loop body returns the return code of TCL_BREAK or TCL_CONTINUE, the loop command can react in such a way as to give the break and continue commands their documented interpretation in loops. Procedure invocation also involves evaluation of a script, the body of the procedure. Procedure invocation provides special treatment when | evaluation of the procedure body returns the return code TCL_RETURN. In that circumstance, the -level entry in the return options dictio- | nary is decremented. If after decrementing, the value of the -level entry is 0, then the value of the -code entry becomes the return code | of the procedure. If after decrementing, the value of the -level entry is greater than zero, then the return code of the procedure is | TCL_RETURN. If the procedure invocation occurred during the evaluation of the body of another procedure, the process will repeat itself up | the call stack, decrementing the value of the -level entry at each level, so that the code will be the return code of the current command | level levels up the call stack. The source command performs the same handling of the TCL_RETURN return code, which explains the similarity | of return invocation during a source to return invocation within a procedure. | The return code of the return command itself triggers this special handling by procedure invocation. If return is provided the option | -level 0, then the return code of the return command itself will be the value code of the -code option (or TCL_OK by default). Any other | value for the -level option (including the default value of 1) will cause the return code of the return command itself to be TCL_RETURN, | triggering a return from the enclosing procedure. EXAMPLES
First, a simple example of using return to return from a procedure, interrupting the procedure body. proc printOneLine {} { puts "line 1" ;# This line will be printed. return puts "line 2" ;# This line will not be printed. } Next, an example of using return to set the value returned by the procedure. proc returnX {} {return X} puts [returnX] ;# prints "X" Next, a more complete example, using return -code error to report invalid arguments. proc factorial {n} { if {![string is integer $n] || ($n < 0)} { return -code error "expected non-negative integer, but got "$n"" } if {$n < 2} { return 1 } set m [expr {$n - 1}] set code [catch {factorial $m} factor] if {$code != 0} { return -code $code $factor } set product [expr {$n * $factor}] if {$product < 0} { return -code error "overflow computing factorial of $n" } return $product } Next, a procedure replacement for break. proc myBreak {} { return -code break } With the -level 0 option, return itself can serve as a replacement for break. | interp alias {} Break {} return -level 0 -code break | An example of using catch and return -options to re-raise a caught error: | proc doSomething {} { | set resource [allocate] | catch { | # Long script of operations | # that might raise an error | } result options | deallocate $resource | return -options $options $result | } | Finally an example of advanced use of the return options to create a procedure replacement for return itself: | proc myReturn {args} { | set result "" | if {[llength $args] % 2} { | set result [lindex $args end] | set args [lrange $args 0 end-1] | } | set options [dict merge {-level 1} $args] | dict incr options -level | return -options $options $result | } | SEE ALSO
break(n), catch(n), continue(n), dict(n), error(n), proc(n), source(n), tclvars(n) KEYWORDS
break, catch, continue, error, procedure, return Tcl 8.5 return(n)
All times are GMT -4. The time now is 09:03 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy