[asterisk-dev] [design] Matching algorithm

[Russell Bryant]

Tony Mountifield wrote:
> In article <48456A0A.3060806 at digium.com>,
> Russell Bryant <russell at digium.com> wrote:
>> My opinion is that treating _x and _X is probably an accidental 
>> oversight, and the code should be updated to treat them the same.
> 
> I originally got bitten by not realizing that lower-case n, x and z were
> special (all the examples in extensions.conf use upper-case). I would use
> lower-case alpha prefixes to extension numbers for certain kinds of dialplan
> processing, and the found this didn't do at all what I expected it to:
> 
> exten => _main-X.,1,Set(CONF=${EXTEN:5})
> 
> So my preference would be for only upper case N, X and Z to be special,
> and lower case to be literal characters. I don't know how many Asterisk
> users do _nxxnxxxxxx instead of _NXXNXXXXXX

Very good point.

After reading this, my opinion has changed to agree with Tony.  :)

I think making only the uppercase versions special is the simplest and 
most straight forward behavior.

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