Shell Programming and Scripting

[[ is a builtin in ksh and supports == .The if statement is quite valid for ksh:

Code:

 $ man ksh | grep "=="
              == !=
              ==     equal;  the result is 1 if both arguments are equal, 0 if
               string == string     strings are equal.

I suspect that the .prog is in dos format. try using dos2unix seaoe_send_mail.prog

@ChublerXL
The "[[ ]]" syntax has been with us since Bourne Shell and is valid in every "sh" and "ksh" I have ever seen.

The "==" syntax is not valid in any "ksh" I have ever seen or any true Posix shell.
I do not have ksh95. What do you have?

Did we identify Operating System the O/P is using?
Or the actual error message?

@methyl in ksh93, within [[ ]] "==" is preferred syntax and "=" is obsolete.

Humm, AFAIK this syntax was not in the Bourne shell

Oops. I stand corrected. In pure Bourne shell the "[[ ]]" syntax did not exist. As I recall it arrived as executable programs called "[[" and "]]" in later versions.
I'd lost track of what a pure Shell is.

Talking of impure Shells. When did "==" become preferred Posix syntax? This is purely out of interest because I come across so many unix Shells that do not support "==" that I have chosen to ignore the syntax for a while.

"==" isn't POSIX syntax, it is preferred in ksh93 within "[[ ]]" . Single "=" is used in (POSIX) single square brackets.

I tried it (with success) on: We have the error from post 1:

Code:

line 9: syntax error in conditional expression
line 9: syntax error near `]]

Which looks like a bash shell error when ^M follows the ]]:

Code:

$ [[ 1 == 3 ]]^M
-bash: syntax error in conditional expression
'bash: syntax error near `]]

This is what makes me suspect that the script file is in dos format and didn't load the ksh shell because of the ^M, and also explains the error message.