On 6/12/25 2:03 PM, Robert Elz wrote:
Date: Thu, 12 Jun 2025 12:26:17 -0400 From: Chet Ramey <chet.ra...@case.edu> Message-ID: <86c23b56-de98-431d-be83-727013b65...@case.edu>| This isn't unreasonable, at least for the change to allow quoted characters | in function names. If that also includes any characters which would need to be quoted to be included in a word (doesn't have to include chars which would be magic when the word is expanded, just the ones which normally affect tokenisation - operators, white space, and the quoting chars) then that will allow a future change to proceed without difficulties.
All of the relevant characters would have to be quoted to appear as part of a WORD, including `$' (which bash has always rejected in function names for some reason). Any quoted character disqualifies the word from being a function name.
But the one which introduced this topic (seeming process substitutions,
except not, as function names) should not be allowed (unless quoted,
so the '<' '(' ')' wouldn't be magic, and so not until quoted words
are permitted, with quote removal being performed).
Yes, that was the other change here -- it was historically treated the same
as a `$'.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU c...@case.edu http://tiswww.cwru.edu/~chet/
OpenPGP_signature.asc
Description: OpenPGP digital signature
