[asterisk-dev] [design] Matching algorithm

[Russell Bryant]

Tilghman Lesher wrote:
> In the matching code, however, there is an anomaly, in that if you use the
> lowercase versions of the common classes, that is "n", "x", and "z", they
> currently match earlier than more specific matches.  That is, "_x" matches
> before "_[1-4]", which matches before "_X".
> 
> 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?

My opinion is that treating _x and _X is probably an accidental 
oversight, and the code should be updated to treat them the same.

-- 
Russell Bryant
Senior Software Engineer
Open Source Team Lead
Digium, Inc.