[EMAIL PROTECTED] wrote:
> When trying to produce an exclamation mark (!) inside a quoted
> string is behaving differently from expected. I cannot see a
> way of producing an exclamation mark inside a doubly-quoted
> (") string in the bash prompt.
You are correct. However
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE
Configuration Information [Automatically generated, do not change]:
Machine: i586
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i586'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i586-mandriva-linux-gnu'
-DCONF_VENDOR='mandriva' -DLOCALEDIR='/usr/share/locale' -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Chet Ramey wrote:
>> Even so, if neither -f nor -v are given, you should apply both naming rules.
>
> If neither option is supplied, the name is required to refer to a variable,
> and the variable naming rules must be followed.
>
> The real problem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: x86_64-pc-linux-gnu-gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-l
Thanks for your reply. That would certainly help.
Regards,
Ken
-Original Message-
From: Chet Ramey [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 16, 2007 9:51 PM
To: Ken Failbus
Cc: Andreas Schwab; bug-bash@gnu.org; [EMAIL PROTECTED]
Subject: Re: bash -n doesn't seem to catch all syn
> Even so, if neither -f nor -v are given, you should apply both naming rules.
If neither option is supplied, the name is required to refer to a variable,
and the variable naming rules must be followed.
The real problem was ever allowing functions with invalid names to be created.
Chet
--
``Th
