[asterisk-dev] case sensitivity with global variables

[Tilghman Lesher]

On Wednesday 16 June 2010 01:38:45 Olle E. Johansson wrote:
> 15 jun 2010 kl. 20.26 skrev Tilghman Lesher:
> > On Tuesday 15 June 2010 12:57:19 Jared Smith wrote:
> >> ----- Original Message -----
> >>
> >>> When using GLOBAL() function it looks like that querying is case
> >>> sensitive, but reading no (as it overwrites the existing variable).
> >>> This is inconsistent with normal channel variables which are always
> >>> case insensitive:
> >>
> >> I was under the impression that Asterisk channel variables were always
> >> case sensitive... Have I missed a change along the way?
> >
> > As far as I know, both global and channel variables are supposed to be
> > case- sensitive, other than a few DEPRECATED builtin variables that have
> > now been largely replaced with dialplan functions.
>
> Agree, but not with the DECPRECATED fact. Did Russell not change the policy
> to "do not deprecate anything unless we have to". I don't think we have to
> remove those variables and break a massive amount of dialplans out there.

No, we still deprecate things that we prefer people not to use.  The only
major difference is that we will not schedule their removal, unless their
presence meets one of a number of guidelines, such as a) security, b)
difficulty of maintenance, or c) interference with a new feature.  Barring
those reasons for removal, a deprecated item is free to remain forever.

-- 
Tilghman Lesher
Digium, Inc. | Senior Software Developer
twitter: Corydon76 | IRC: Corydon76-dig (Freenode)
Check us out at: www.digium.com & www.asterisk.org