2023年2月7日(火) 0:40 Chet Ramey <chet.ra...@case.edu>: > On 2/4/23 8:02 PM, Koichi Murase wrote: > > In the previous time that I raised the discussion about ``no-argument > > return in trap handlers'', I directly posted an email to the mailing > > list [1]. Fortunately, I got about ten replies but later, > > unfortunately, it was finally forgotten without any conclusion. > > That's not the case. kre wrote up a wonderfully detailed interpretation > request: > > https://www.austingroupbugs.net/view.php?id=1602 > > and it was ultimately resolved with the interpretation in the last comment, > which is pretty close to what you wanted. > > I applied a change for that in early November, after I released bash-5.2, > and revised it in mid-December.
Thank you for the information. Yes, I actually noticed them and was aware of the entire story. As you know, after there was another similar report in bug-bash [1], there was a discussion again in its replies, where kre has promised to create an issue in the Austing Group. Then, I was checking the mailing list and found that this was processed. I'm also constantly checking the devel branch so I also noticed that Bash was also fixed in some way (thank you for the fix!), though I confess that I just looked at the diff and haven't yet examined the behavior after the fix. [1] https://lists.gnu.org/archive/html/bug-bash/2022-08/msg00009.html By the way, I got a reply from the chair, Andrew, yesterday and could get my account in the Austing Group Issue Tracker. I'll later submit an issue about the implementation extension of function names with slashes. -- Koichi
