[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: weird ksh eval behavior

From: Paul Eggert
Subject: Re: weird ksh eval behavior
Date: Fri, 02 Dec 2005 11:21:07 -0800
User-agent: Gnus/5.1007 (Gnus v5.10.7) Emacs/21.4 (gnu/linux)

Ralf Wildenhues <address@hidden> writes:

> I noticed a couple of nits:

Thanks for mentioning them.  I installed this further patch:

2005-12-02  Paul Eggert  <address@hidden>

        * doc/autoconf.texi (Limitations of Builtins): Fix typos in previous
        patch, noted by Ralf Wildenhues.

--- autoconf.texi       1 Dec 2005 21:02:40 -0000       1.934
+++ autoconf.texi       2 Dec 2005 19:19:23 -0000       1.935
@@ -11127,7 +11127,7 @@ EOF
 @item @command{eval}
 @c -----------------
 @prindex @command{eval}
-In some shell implementations (e.g., @command{ash}, OpenBSD 3.8
+In some shell implementations (e.g., older @command{ash}, OpenBSD 3.8
 @command{sh}, @command{pdksh} v5.2.14 99/07/13.2, and @command{zsh}
 4.2.5), the arguments of @samp{eval} are evaluated in a context where
 @samp{$?} is 0, so they exhibit behavior like this:
@@ -11137,7 +11137,7 @@ $ false; eval 'echo $?'
 @end example
-The correct behavior here is to assign a nonzero value to @samp{foo},
+The correct behavior here is to output a nonzero value,
 but portable scripts should not rely on this.
 You should not rely on @code{LINENO} within @command{eval}.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]