Ken Failbus wrote:
> When I specify on command-line "bash -n ". Bash doesn't
> check for valid syntax errors. E.g. if variable is missing a "$" infront
> of it while assigning a value. This is not catched by bash.
> ### example code
> p=hello
> e=world
> If [ p != $e ];then
> echo "not equa
"Ken Failbus" <[EMAIL PROTECTED]> writes:
> Hi Guys,
>
> When I specify on command-line "bash -n ". Bash doesn't
> check for valid syntax errors. E.g. if variable is missing a "$" infront
> of it while assigning a value.
Bash is not Perl. Your example code is perfectly valid.
Andreas.
--
Andr
Ken Failbus wrote:
> When I specify on command-line "bash -n ". Bash doesn't
> check for valid syntax errors. E.g. if variable is missing a "$" infront
> of it while assigning a value. This is not catched by bash.
Unfortunately what you are describing is not a syntax error. It is
perfectly valid
Hi Guys,
When I specify on command-line "bash -n ". Bash doesn't
check for valid syntax errors. E.g. if variable is missing a "$" infront
of it while assigning a value. This is not catched by bash. Is there a
more specific option that should be specified to bash to check for
syntax errors.
Regard
Hi Chet,
I was able to solve the problem. By uncommenting a line in our script
that was setting a "set -m" for Solaris platform I was able to resolve
this issue.
Thanks to everyone for looking into this one and advising.
Regards,
Ken
-Original Message-
From: Chet Ramey [mailto:[EMAIL PR
