Ok, I see. Thank you for the answer.
I've already found a program (yaourt) that wreaks havoc because of
this, I gave its developers a heads up.
The cause of my question is that I want to use your readline devel
branch. First, I thought I would need to use the bash devel branch
too, but then I realized that just recompiling the stable branch
against readline devel would be enough. So the disruptive continue
behaviour is not really an issue for me, as I've thought at first.
Nevertheless, there is still the problem of recompiling and replacing
the system-wide /bin/bash because most of the bash scripts will use
it. This is easy in my arch linux but not so easy in production
servers where I use readline a lot.
Do you have plans to backport the improvements in readline that
doesn't require a change in the binary interface? If not, would it be
too difficult to do it myself?
Cheers
--
Carlos
On Sat, Oct 10, 2015 at 1:51 PM, Chet Ramey <chet.ra...@case.edu> wrote:
> On 10/10/15 9:36 AM, Carlos Pita wrote:
>> Hi Chet,
>>
>> consider the following program:
>>
>> yyy() {
>> continue
>> }
>>
>> xxx() {
>> while true; do
>> echo x
>> yyy
>> echo y
>> break
>> done
>> }
>>
>> xxx
>>
>> In the bash devel branch it will ignore the continue and echo
>>
>> x
>> y
>
> The change was made intentionally. Historical versions of sh ignore (or
> more precisely reset) the loop state when entering a shell function, so
> the continue doesn't have any effect. Posix doesn't say anything specific
> about it, but it doesn't call out a change from the historical behavior,
> so it came up reported as a bug.
>
> The discussion about the change took place on the dash mailing list,
> but the gmane.org archives are down right now so I can't give you a URL.
>
> 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/
