Date: Wed, 11 Jun 2025 10:09:46 -0400
From: Chet Ramey <chet.ra...@case.edu>
Message-ID: <f01ae1f4-a9c9-419d-8f45-4e4378dcb...@case.edu>
| That wouldn't have been backwards compatible, so I didn't add quote
| removal.
Really, in what cases? Like Koichi Murase showed, I can't find any
way to get a quote char (without objection) into a 5.2 function name
in its definition, and if it can't be included in that version, it cannot
possibly be incompat to remove it (other than with 5.3 alpha releases,
and I don't think they matter at all.)
If some ancient version of bash permitted stray unquoted quoting chars in
func names, then the backward compat for that looks to have been broken
already in 5.2, and 5.1, which have certainly been around long enough to
expose any issues that might have caused (not that I believe that actually
happened.)
kre
