[asterisk-dev] [design] Matching algorithm

[Tilghman Lesher]

On Wednesday 04 June 2008 09:24:06 Jay R. Ashworth wrote:
> On Tue, Jun 03, 2008 at 03:20:43PM -0500, Tilghman Lesher wrote:
> > > To answer your question from my perspective, given:
> > > > > Now, we are not going to change this behavior in 1.4, certainly.
> > > > > That has the potential to break currently working dialplans, and
> > > > > where we can reasonably foresee such an outcome, we'd like to
> > > > > avoid that.
> > > > >
> > > > > However, this is certainly an unintended behavior, and the
> > > > > question then becomes, do we document this as a way to override
> > > > > the pattern match algorithm, or do we change the lowercase class
> > > > > letters to behave the same as the uppercase class letters?
> > >
> > > Unless I'm misunderstanding you, the latter alternative directly
> > > contradicts the assertion in the first graf: you can't. If you think
> > > people are depending on the undocumented "override" behavior, then
> > > you have to maintain it.
> >
> > I disagree.
>
> You disagree that "we are not going to change this behavior" conflicts
> with "[do] we change the lowercase letters to behave the same..."?
>
> Cause that's what I asserted.

You're selectively quoting.  We are not going to change the behavior *in*
*1.4*.  We *are* going to make a change in 1.6/trunk.

-- 
Tilghman