Vincent Lefevre wrote:
> An EXIT trap is executed when the process is killed, e.g. by the
> SIGTERM signal, which breaks traditional sh compatibility
A lot of POSIX required behavior breaks traditional Bourne sh
compatibility.
> and, IMHO, is not POSIX-compliant (see the explanations in the
bash's "test" builtin can report the wrong results in many
circumstances (e.g. read-only filesystems, noexec filesystems, ACLs,
NFS, AFS, setuid executables, etc) because it uses stat() rather than
access() for the unary -w, -r, -x, etc.
This has come up before:
http://lists.gnu.org/archive/html/b
Hello,
This is a resend of a message I sent back in May since I never
received a reply to that message.
-Brett
-- Forwarded message --
From: Brett Kail <[EMAIL PROTECTED]>
Date: May 18, 2005 9:17 PM
Subject: read -n is confused by \
To: bug-bash@gnu.org
Hello,
Description:
Mike Frysinger wrote:
> i know when you enable strict posix behavior, you cant use dashes in function
> names ... but `typeset -f` seems to always reject the dash:
`typeset' requires all of its arguments to be legal identifiers. There
is a slight inconsistency there; I will have to think it over
i know when you enable strict posix behavior, you cant use dashes in function
names ... but `typeset -f` seems to always reject the dash:
[EMAIL PROTECTED] 0 ~ $ some_func() { :; }
[EMAIL PROTECTED] 0 ~ $ some-func() { :; }
[EMAIL PROTECTED] 0 ~ $ bash --posix
bash-3.1$ some_func() { :; }
bash-3.
