|
From: | Roman Rakus |
Subject: | . (source) builtin behavior changed when commands are in {} braces |
Date: | Fri, 15 Aug 2008 14:31:11 +0200 |
User-agent: | Thunderbird 2.0.0.16 (X11/20080723) |
In previous version (3.0) bash continue after {} braces. For example: { readonly a a=10 } || : echo helloIn bash 3.2 we've got error message about readonly variable, but "hello" is not printed. Is this right behavior or bug? I investigate this problem and found, that there is added top_level_cleanup () function. I don't know what is going on in this function, but probably is changing top_level (saved stack context) and further calling jump_to_top_level () jumps elsewhere then in bash 3.0. For now I comment out calling top_level_cleanup(), but I know, that there is better way.
rrakus.vcf
Description: Vcard
[Prev in Thread] | Current Thread | [Next in Thread] |