On 9/27/14, 8:49 PM, Eric Blake wrote:
> On 09/27/2014 05:59 PM, Chet Ramey wrote:
>> On 9/27/14, 4:29 PM, Eric Blake wrote:
>>> On 09/27/2014 12:53 PM, Chet Ramey wrote:
>> We have an opportunity to close up a potential problem here, at least
>> with respect to function names containing `/'.
>
> As I said in a later mail, I'm now definitely leaning towards your
> desire to exclude '/', and may I also add '=', as two characters that
> will be blacklisted from valid function names both in the shell and
> during import/export, because they are just too risky. I haven't yet
> come up with any reason to blacklist any other non-metacharacter, and
> you already reject any metacharacter that requires quoting.
I'm just going to include slash for right now, since `=' doesn't cause
any real problems, because you're effectively not able to export it with
the current version.
>> Yeah, but what I was talking about was allowing non-identifiers as valid
>> function names.
>
> Where does POSIX forbid the use of a non-identifier as a valid function
> name?
Yes, it's an application requirement. Regardless, all the versions of bash
we're talking about here reject non-identifiers.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
