topic Re: what is wrong with this script in Operating System - HP-UX

what is wrong with this script

Hanry Zhou — Tue, 15 Jun 2004 11:58:24 GMT

#!/bin/ksh

for xyz in `cat filelist`
do
con=`echo $xyz`
if [[ $con == "s" ]]
then
echo "in then"
else
echo "in else"
fi
done

I don't know what is the wrong with the script,
the problem is the login always fall in "else" section even though con="s"?

Please help me out. This script is running on linux serverm, but using /bin/ksh.

Re: what is wrong with this script

Victor Fridyev — Tue, 15 Jun 2004 12:05:58 GMT

Hi,

Why do you use double brackets ?

The right form is :
if [ $con=="s" ]; then

etc.

HTH

Re: what is wrong with this script

A. Clay Stephenson — Tue, 15 Jun 2004 12:06:48 GMT

First, you don't need con; simply use xyz and forget the con=`echo $xyz`

Secondly, it's "=" not "=="

Thirdly, protect you if's with quotes so that null variables don't kill you.

for xyz in $(cat filelist)
do
if [[ "${xyz}" = "s" ]]
then
echo "in then"
else
echo "in else"
fi
done

Re: what is wrong with this script

Sridhar Bhaskarla — Tue, 15 Jun 2004 12:08:13 GMT

Hi,

== is to be replaced with =.

It should work then.

-Sri

Re: what is wrong with this script

Hanry Zhou — Tue, 15 Jun 2004 12:11:07 GMT

Victor,

If I chage the way you suggested, the logic will forever fall in "then" section even though $con is not equal to "s"

Re: what is wrong with this script

Hanry Zhou — Tue, 15 Jun 2004 12:21:17 GMT

clay,

the reason I use con=`echo $xyz` is because I need to run a command based on the value of $xyz, and assign the result to "con", so in my realy case, it is not con=`echo $xyz`. I just use it to replace my real command.

2nd, if I change the way you suggested, it will forever fall in "else" section.

Re: what is wrong with this script

Hanry Zhou — Tue, 15 Jun 2004 12:41:59 GMT

If I have the string like " s", "s ", or " s ", how do I get rid of the empty strings in front or after "s"?

Re: what is wrong with this script

A. Clay Stephenson — Tue, 15 Jun 2004 15:07:51 GMT

Okay do this to strip the spaces:

con=$(echo "${con}" | tr -d ' ')

Re: what is wrong with this script

Tim D Fulford — Tue, 15 Jun 2004 15:14:59 GMT

Or sed

con=$(sed "s/\ //g" $(echo $xyz))

Tim

Re: what is wrong with this script

Hein van den Heuvel — Tue, 15 Jun 2004 18:16:57 GMT

Now that you mention spaces, indicating a worry about detailed matching you should probably start to look at regular expression.
You may want to replace the whole job with some perl. For example:

perl -ne 'if (/^\s*s\s*$/) {print "then: $_" } else {print "else: $_"}' filelist

or

perl -pe 'print (("s" eq split[0])? "then: " : "else: ")' x filelist

This looks for a line with a single "s" and optional whitespace.

re explanation:
^ = begin of line
\s = whitespace (space, tab)
\s* = zero or none whitespace
s = "the real McCoy"
$ = end of line

In the othere solution: split = splits default input line ($_) for words based on whitespace. The [0] selects the firs word.

perl arguments

-e = "script on command line"
-n = implied loop through STDIN, no print
-p = print $_ at end of implied loop itteration through STDIN

Cheers,
Hein.

perl -pe 'if (/^\s*s\s*$/) {print "then: "} else {print "else: "}' filelist

perl -pe 'print ((/^\s*s\s*$/)? "then: " : "else: ")' filelist

Re: what is wrong with this script

curt larson_1 — Tue, 15 Jun 2004 20:34:51 GMT

let see
tics for comand subsitiution are obsolete
echo statement is obsolete
== for testing of equality isn't implemented

your script should something like

#!/usr/bin/ksh

for xyz in $(cat filelist)
do
con=${print $xyz}
#although con="$xyz" does the samething only faster

if [[ "$con" = "s" ]]
then
print "in then"
else
print "in else"
fi
done

and for removeing characters
print "$xyz" | tr -cd "[:alnum:]"
which will delete all characters that aren't alphanumeric