Sponsored Content
Top Forums Shell Programming and Scripting gcd.sh script doesn't work... Post 302159418 by kantze on Thursday 17th of January 2008 06:55:18 PM
Old 01-17-2008
gcd.sh script doesn't work...

Hi there. I'm new to scripting in bash shell and I have this problem.
I'm trying to make a script that returns the greatest common divisor of two integer numbers according to Euclid's algorithm...

Here is, what I've done:
Code:
#!/bin/bash

m=$1
n=$2

while [ "$n" != 0 ]
do
if [ "$m" -gt "$n" ]; #line 8
then m=$m-$n
else n=$n-$m
fi
done
echo $n

and I get an error message: line 8:integer exrpession expected
I run the gcd.sh writing in the terminal
Code:
./gcd.sh 14 28

where 14 and 28 are integers, right?
So, what's the problem? Could you please tell me what should I write?
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Shel Script doesn't work from Exceed

Hi, I am using this script to load up my Oracle Databases, but when I log in through Exceed, it hangs. Can anyone tell me what else I need to add to make this work?? Details ****************************************************************************************************... (11 Replies)
Discussion started by: dnkansah
11 Replies

2. UNIX for Dummies Questions & Answers

Script doesn't work, but commands inside work

Howdie everyone... I have a shell script RemoveFiles.sh Inside this file, it only has two commands as below: rm -f ../../reportToday/temp/* rm -f ../../report/* My problem is that when i execute this script, nothing happened. Files remained unremoved. I don't see any error message as it... (2 Replies)
Discussion started by: cheongww
2 Replies

3. Shell Programming and Scripting

script doesn't work in another distribution

Hi everybody: I usually use Mandriva distro (in my laptop), and I have made some scripts. These scripts work correctly but now, in other computer which is installed Ubuntu don't work, and I have this error message: The script is: ..... echo "Your option is:" echo read option case... (1 Reply)
Discussion started by: tonet
1 Replies

4. Shell Programming and Scripting

Expect script doesn't work under crontab

Hi All, Using Expect script when I run it manually it works. But when I put the entry in crontab, the job is still running after 15 hours. The script was created as root. I don't think it's a permission issue. Any idea? This is what I have under root crontab... 00 18 * * 1-5... (4 Replies)
Discussion started by: samnyc
4 Replies

5. Shell Programming and Scripting

Help with script.. it Just doesn't work

Hello,, Im verry new to scripting and have some problems with this script i made.. What it does: It checks a directory for a new directory and then issues a couple of commands. checks sfv - not doing right now checks rar - it checks if theres a rar file and when there is it skips to... (1 Reply)
Discussion started by: atmosroll
1 Replies

6. Shell Programming and Scripting

two grep in one script doesn't work?

Hi there, the following script doesn't work. the first part works, then the second 'grep' fails with ': not found'. However, if I take out the second part (starting with the grep command) and put in a seperate script, it works. everyone know what's wrong here? no two 'grep' in one script, that... (2 Replies)
Discussion started by: monkey77
2 Replies

7. Shell Programming and Scripting

Script doesn't work in loop but does if not

I have a script that only works if I remove it from the looping scenario. #!/bin/bash # Set the field seperator to a newline ##IFS=" ##" # Loop through the file ##for line in `cat nlist.txt`;do # put the line into a variable. ##dbuser=$line echo "copying plugin..." ... (6 Replies)
Discussion started by: bugeye
6 Replies

8. Shell Programming and Scripting

my script doesn't work :(

i have this script and when i ejecute it, the console tell me this " sintax error line 41 unexpected element "}" " is the sintaxis ok? #!/bin/bash if ;then { exit 0; } if ; then { sudo /etc/init.d/apache2 start; sudo /etc/init.d/mysql start; php5 & nautilus... (3 Replies)
Discussion started by: keiserx
3 Replies

9. Shell Programming and Scripting

[Solved] Script doesn't work..help?

hi, i am trying to run this script.the name of script is final.sh after i run it: #./final.sh & i grep the command # ps -a | grep bash and i see more then one processes runing 3!! Please use code tags how can i solve this problem? my target script must always run in... (8 Replies)
Discussion started by: zigizag
8 Replies

10. Shell Programming and Scripting

Read in script doesn't work

I am trying to run a script to make a simple modification to a number of similar files. The sed works, but after it runs and the differences are displayed, the script does not read ans to start a renaming script if the user answered Y or y.for i in "$@" do sed -f myfile.sed $i >$i.new diff... (2 Replies)
Discussion started by: wbport
2 Replies
docstrip_util(n)					     Literate programming tool						  docstrip_util(n)

__________________________________________________________________________________________________________________________________________________

NAME
docstrip_util - Docstrip-related utilities SYNOPSIS
package require Tcl 8.4 package require docstrip::util ?1.2? docstrip::util::ddt2man text docstrip::util::guards subcmd text docstrip::util::thefile filename ?option value ...? _________________________________________________________________ DESCRIPTION
The docstrip::util package is meant for collecting various utility procedures that may be useful for developers who make use of the doc- strip package in some projects. It is separate from the main package to avoid overhead for end-users. COMMANDS
docstrip::util::ddt2man text The ddt2man command reformats text from the general docstrip format to doctools ".man" format (Tcl Markup Language for Manpages). The different line types are treated as follows: comment and metacomment lines The '%' and '%%' prefixes are removed, the rest of the text is kept as it is. empty lines These are kept as they are. (Effectively this means that they will count as comment lines after a comment line and as code lines after a code line.) code lines example_begin and example_end commands are placed at the beginning and end of every block of consecutive code lines. Brackets in a code line are converted to lb and rb commands. verbatim guards These are processed as usual, so they do not show up in the result but every line in a verbatim block is treated as a code line. other guards These are treated as code lines, except that the actual guard is emphasised. At the time of writing, no project has employed doctools markup in master source files, so experience of what works well is not available. A source file could however look as follows % [manpage_begin gcd n 1.0] % [moddesc {Greatest Common Divisor}] % [require gcd [opt 1.0]] % [description] % % [list_begin definitions] % [call [cmd gcd] [arg a] [arg b]] % The [cmd gcd] procedure takes two arguments [arg a] and [arg b] which % must be integers and returns their greatest common divisor. proc gcd {a b} { % The first step is to take the absolute values of the arguments. % This relieves us of having to worry about how signs will be treated % by the remainder operation. set a [expr {abs($a)}] set b [expr {abs($b)}] % The next line does all of Euclid's algorithm! We can make do % without a temporary variable, since $a is substituted before the % [lb]set a $b[rb] and thus continues to hold a reference to the % "old" value of [var a]. while {$b>0} { set b [expr { $a % [set a $b] }] } % In Tcl 8.3 we might want to use [cmd set] instead of [cmd return] % to get the slight advantage of byte-compilation. %<tcl83> set a %<!tcl83> return $a } % [list_end] % % [manpage_end] If the above text is (suitably unindented and) fed through docstrip::util::ddt2man then the result will be a syntactically correct doctools manpage, even though its purpose is a bit different. It is suggested that master source code files with doctools markup are given the suffix ".ddt", hence the "ddt" in ddt2man. docstrip::util::guards subcmd text The guards command returns information (mostly of a statistical nature) about the ordinary docstrip guards that occur in the text. The subcmd selects what is returned. counts List the guard expression terminals with counts. The format of the return value is a dictionary which maps the terminal name to the number of occurencies of it in the file. exprcount List the guard expressions with counts. The format of the return value is a dictionary which maps the expression to the num- ber of occurencies of it in the file. exprerr List the syntactically incorrect guard expressions (e.g. parentheses do not match, or a terminal is missing). The return value is a list, with the elements in no particular order. expressions List the guard expressions. The return value is a list, with the elements in no particular order. exprmods List the guard expressions with modifiers. The format of the return value is a dictionary where each index is a guard expres- sion and each entry is a string with one character for every guard line that has this expression. The characters in the entry specify what modifier was used in that line: +, -, *, /, or (for guard without modifier:) space. This is the most primitive form of the information gathered by guards. names List the guard expression terminals. The return value is a list, with the elements in no particular order. rotten List the malformed guard lines (this does not include lines where only the expression is malformed, though). The format of the return value is a dictionary which maps line numbers to their contents. docstrip::util::thefile filename ?option value ...? The thefile command opens the file filename, reads it to end, closes it, and returns the contents. The option-value pairs are passed on to fconfigure to configure the open file channel before anything is read from it. SEE ALSO
docstrip, doctools, doctools_fmt KEYWORDS
COPYRIGHT
Copyright (c) 2003-2005 Lars Hellstrom <Lars dot Hellstrom at residenset dot net> docstrip 1.2 docstrip_util(n)
All times are GMT -4. The time now is 08:10 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy