On 3/9/14 2:57 PM, Dan Douglas wrote:
>> Cause the function call to recurse infinitely. I would understand if
>> this is labeled as a feature, rather than a bug (in the sense that
>> the user shouldn't be putting return inside a return trap :), so one
>> can safely assume that if they did it, it's because they wanted the
>> infinite recursion).
>>
[...]
>
> I know we've discussed this off-list, but I'll restate that I've known
> about this for a long time and never considered it a bug. The return
> status currently remains that of the last command or return evaluated
> prior to the trap, which is consistent with my reading of the spec.
While it was clearly not the original intention of the code, the current
behavior has been in place for many years. I know how to change it if
and when I want, but for now I will leave it alone.
Chet
--
``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/
