----- Original Message ----- > From: "Ira" <i...@extrasensory.com> > To: "Asterisk Users Mailing List - Non-Commercial Discussion" > <asterisk-users@lists.digium.com> > Sent: Tuesday, October 2, 2012 8:11:32 PM > Subject: Re: [asterisk-users] Case-sensitivity of Dialplan variables. > > > 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. Just some thoughts in regards to the concerns brought up. Michael L. Young (elguero) -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
