With the current git head (and 4.3):
$ ./bash -c 'eval() { echo function; }; set -o posix; type eval; eval echo not
function'
eval is a function
eval ()
{
echo function
}
not function
$ ./bash --version
GNU bash, version 4.4.0(1)-alpha (x86_64-unknown-linux-gnu)
[...]
"type eval" should retu
On 07/21/2015 05:07 AM, Stephane Chazelas wrote:
> With the current git head (and 4.3):
>
> $ ./bash -c 'eval() { echo function; }; set -o posix; type eval; eval echo
> not function'
'eval' is a special built-in, and as such, cannot be usefully defined as
a function, because the shell rules for
2015-07-21 08:07:15 -0600, Eric Blake:
> On 07/21/2015 05:07 AM, Stephane Chazelas wrote:
> > With the current git head (and 4.3):
> >
> > $ ./bash -c 'eval() { echo function; }; set -o posix; type eval; eval echo
> > not function'
>
> 'eval' is a special built-in, and as such, cannot be usefull
Bash will report error if you define function, which named the same as special
builtin commands, in POSIX mode:
$ bash --norc --posix$ bash-4.3$ eval() { echo func;}bash: `eval': is a special
builtin
The problem here is bash doesn't forget those type of functions if they were
defined before POSI
On 7/16/15 12:05 AM, Patrick Plagwitz wrote:
>> This is another case of the scenario most recently described in
>>
>> http://lists.gnu.org/archive/html/bug-bash/2014-03/msg00108.html
>>
>> In this case, python appears to catch the SIGINT (it looks like a
>> KeyboardInterrupt exception), print the
