|
From: | Chet Ramey |
Subject: | Re: unset does not remove functions like a[b] unless -f is specified |
Date: | Fri, 3 Feb 2023 11:55:15 -0500 |
User-agent: | Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.7.0 |
On 2/2/23 3:02 PM, Dale R. Worley wrote:
Greg Wooledge <greg@wooledge.org> writes:I'd be totally OK with restricting the function namespace a bit more. Function names should not be allowed to contain backticks or less-than or greater-than signs (in my opinion). I'm still undecided about parentheses, but I'm leaning toward "denied".I'd be perfectly fine if function names had to be "names", and my memoryis that old versions of Bash enforced that.
That is the opposite of how it went. From the beginning, bash had very few limitations on function names (dollar sign, unquoted, all digits, etc.). It was when I added posix mode changes between bash-1.13 and bash-1.14 that the restrictions on names came in. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
[Prev in Thread] | Current Thread | [Next in Thread] |