[asterisk-users] Gosub behavior change <=1.6.0.5 to 1.6.0.6

[Tilghman Lesher]

On Wednesday 25 February 2009 11:19:08 sean darcy wrote:
> Tilghman Lesher wrote:
> > On Wednesday 25 February 2009 09:51:23 Klaus Darilion wrote:
> >> Tilghman Lesher schrieb:
> >>> On Tuesday 24 February 2009 16:07:52 Klaus Darilion wrote:
> >>>> Barry L. Kline wrote:
> >>>>> that is supposed to gosub into the incoming extension at priority 1.
> >>>>> Versions before 1.6.0.6 would drop into the incoming,i,1 priority if
> >>>>> the requested extension wasn't present in the incoming context.
> >>>>
> >>>> Really strange that Goto and Gosub behave different.
> >>>
> >>> If Goto behaves that way, that's a bug.  As stated in a prior email,
> >>> the "i" extension should only be implicitly invoked when waiting for a
> >>> new extension and the typed extension does not match anything.
> >>
> >> FYI: If you take a look at the history of
> >> http://www.voip-info.org/wiki/index.php?page=Asterisk+i+extension you
> >> will find out that the old behavior is there since at least Nov. 2005,
> >> and probably used since then.
> >
> > voip-info.org is best known for being often wrong.
>
> I think the point being made was that a lot of people thought this was a
> feature, not a bug.
>
> I assume you're asserting the the dev's did not expect this behaviour,
> even if a large group of users did.
>
> That's OK. But there's still the question about why this behaviour is so
> bad/inconsistent/something that it should be changed. Simply labeling it
> a bug is just a conclusion. Why is it a bug???

It's a bug, because the "i" extension has a very limited intended usage, and
any additional cases where the "i" extension is implicitly invoked is
therefore a bug.

This thread has convinced me not to change Goto in 1.6.0, but I absolutely
defend fixing this bug in Gosub, given that I'm the designer of it, and it was
never supposed to fail into the "i" extension.

-- 
Tilghman