[asterisk-dev] Case-sensitivity of Dialplan variables.

[Paul Belanger]

On 12-10-02 11:44 AM, Michael L. Young wrote:
> ----- Original Message -----
>> From: "Andrew Latham" <lathama at gmail.com>
>> To: "Asterisk Developers Mailing List" <asterisk-dev at lists.digium.com>
>> Sent: Tuesday, October 2, 2012 10:59:36 AM
>> Subject: Re: [asterisk-dev] Case-sensitivity of Dialplan variables.
>>
>> On Tue, Oct 2, 2012 at 10:52 AM, Walter Doekes
>> <walter+asterisk-dev at osso.nl> wrote:
>>>>> ("HASH" would be evaluated properly but "hash") would not. My
>>>>> personal
>>>>> opinion is that all variable evaluations should be
>>>>> case-sensitive. I
>>>>> don't feel all that strongly about it though and could easily be
>>>>> swayed the other way if people respond overwhelmingly in
>>>>> opposition.
>>>
>>>
>>> My opinion: case sensitive.
>>>
>>> Don't delegate stuff to runtime (strcasecmp) that a good editor
>>> and/or good
>>> eyes should cover.
>>>
>>> There are always going to be case sensitive bits left (dialplan
>>> options, for
>>> starters). Better do everything in the proper case the first time.
>>>
>>>
>>> I'd consider writing a basic on-dialplan-load check to warn people
>>> of case
>>> mistakes if that sways the opinion towards case-sensitive.
>>>
>>> Regards,
>>> Walter
>>
>> I think Walter touches upon a good point.  There are case sensitive
>> options for apps, functions and the like.
>>
>> I would vote "case sensitive".
>
> +1 for case sensitive.  It just feels like the right thing to do and feels more natural for those working in a Linux environment anyways.
>
+1


-- 
Paul Belanger | PolyBeacon, Inc.
Jabber: paul.belanger at polybeacon.com | IRC: pabelanger (Freenode)
Github: https://github.com/pabelanger | Twitter: 
https://twitter.com/pabelanger