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

[Ira]

At 07:59 PM 10/2/2012, you wrote:
> >
> > Given that many of the users were not programmers and didn't likely
> > grow up in a case sensitive world I'd also vote for case
> > insensitivity. I fall into that category, I grew up with dBase,
> > Clipper and VB and case issues get me all the time when I program in
> > C.
> >
> > Allowing case insensitivity does not stop someone from using case
> > consistently and While I guess there could be a reason why you'd want
> > to use the word hash in the forms hash, Hash and HASH and have them
> > be 3 different items, I'm guessing that the people trying to get
> > their feet wet moving from Asterisk-Now to Asterisk would be confused
> > to say the least if someone did that in example code.
>
>While true that most users are probably not programmers, most people 
>administering Asterisk would be system / network admins, 
>correct?  System admins and networking admins are used to working in 
>environments such as Linux where variables and file names are case sensitive.
>
>If someone is moving from a GUI interface to CLI, then they 
>would/should know that case sensitivity is important and therefore 
>the change shouldn't pose a problem.

I'm not a system / network admin, at least not for Linux. I have one 
Linux machine, it runs Asterisk and Samba. I can usually make 
Asterisk do what I want. Samba works but I have little to no idea 
why.  I run "yum update" occasionally and I run V11 trunk or whatever 
the proper name would be for the development version.

If there was a compiler and declared variables then case makes 
perfect sense. Without that, I'd never get a C program to work.

I know people want case sensitivity, it's the "right" way to do it, 
but how does it help Asterisk?

Does anyone have configurations that would be broken by case insensitivity?

If not, then what is the upside of enforcing case sensitivity?

Ira