[asterisk-dev] case sensitivity with global variables

[Klaus Darilion]

Hi Tilghman!

I have update to 1.6.2-branch and tested again:

Set(FOO=BAR);
Verbose(${FOO});          BAR
Verbose(${foo});          BAR
Set(foo=bar);
Verbose(${FOO});          bar
Verbose(${foo});          bar

Set(GLOBAL(FOO2)=BAR);
Verbose(${GLOBAL(FOO2)});  BAR
Verbose(${GLOBAL(foo2)});  <null>
Set(GLOBAL(foo2)=bar);
Verbose(${GLOBAL(FOO2)});  BAR
Verbose(${GLOBAL(foo2)});  bar
Verbose(${FOO2});          bar
Verbose(${foo2});          bar

So it seems that global variables, when handled via the GLOBAL function, 
are now case sensitive.

But normal channel variables, and global channel variables accessed 
directly, are still case insensitive.

regards
Klaus


Am 16.06.2010 17:13, schrieb Tilghman Lesher:
> On Wednesday 16 June 2010 06:18:20 Klaus Darilion wrote:
>> Am 15.06.2010 20:26, schrieb 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.
>>
>> So, what is the conclusion?
>>
>> If variables should be case sensitive I will file a bug report.
>>
>> If the "case sensitivity" policy was introduced with trunk, I can test
>> trunk too.
>
> I found the issue you referred to and fixed it in all 3 branches, yesterday.
> http://lists.digium.com/pipermail/asterisk-commits/2010-June/043413.html
>