On Tue, 2012-10-02 at 17:11 -0700, Ira wrote:
At 02:19 PM 10/1/2012, you wrote:
So respond here and let me know what you think. I got a couple of replies on
the -dev list and they said that this would be good to put out on the -users
list too.
Mark Michelson
In true Republican fashion,
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
Il 01/10/2012 23.15, Mark Michelson ha scritto:
https://issues.asterisk.org/jira/browse/ASTERISK-20163
The issue involves case-sensitivity of channel and global variables
in the dialplan.
+1 for case-sensitive variables everywhere.
I'm glad to see that this inconsistency issue will be
On Monday 01 October 2012, Danny Nicholas wrote:
I propose that dialplan variables need to be made consistent in their
evaluation. We need to choose either to be always case-sensitive or always
case-insensitive. The problem is, I don't know which of these changes would
have a larger effect on
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.
I'm in favor of
- Original Message -
From: Ira i...@extrasensory.com
To: Asterisk Users Mailing List - Non-Commercial Discussion
asterisk-users@lists.digium.com
Sent: Wednesday, October 3, 2012 3:21:50 AM
Subject: Re: [asterisk-users] Case-sensitivity of Dialplan variables.
At 07:59 PM 10/2/2012
On Tuesday 02 Oct 2012, Mark Michelson wrote:
[snip]
Some of you might be eager to propose a configuration option to
decide which it should be. I'm sick of having hundreds of options
in Asterisk to slightly tweak the behavior one way or another. This
needs to go one way or the other, not be
- Original Message -
From: Raj Mathur (राज माथुर) r...@linux-delhi.org
To: asterisk-users@lists.digium.com
Sent: Wednesday, October 3, 2012 10:49:30 AM
Subject: Re: [asterisk-users] Case-sensitivity of Dialplan variables.
snip
So here's the proposal: make case-insensitivity
- Original Message -
From: Matthew Jordan mjor...@digium.com
To: Asterisk Users Mailing List - Non-Commercial Discussion
asterisk-users@lists.digium.com
Sent: Wednesday, October 3, 2012 12:17:56 PM
Subject: Re: [asterisk-users] Case-sensitivity of Dialplan variables.
From Mark's
On 02/10/12 09:02 PM, Vladimir Mikhelson wrote:
snip
First you need to consider compatibility with currently supported
packages which include auto-generated dial plans like AsteriskNow, PIAF,
etc. If you plan to break their functionality you need to at least
coordinate your move with the
On 03/10/12 11:49 AM, Raj Mathur (राज माथुर) wrote:
In short, my vote goes for case-sensitivity with a grace period for
switching over.
I disagree. Migrating between major versions should never be something
like installing Asterisk 12 over an existing Asterisk 11 (or earlier)
system. It
On 03/10/12 03:01 PM, Michael L. Young wrote:
We are probably a year away from seeing a release for the version of Asterisk
where this change would occur. We are two years away from an LTS version of
Asterisk. So, I think there would be plenty of time for evaluation and testing
to be
] Case-sensitivity of Dialplan variables.
Hi!
I've been confronted with an interesting issue to resolve. The issue is
located here:
https://issues.asterisk.org/jira/browse/ASTERISK-20163
The issue involves case-sensitivity of channel and global variables in the
dialplan. Current behavior
At 02:19 PM 10/1/2012, you wrote:
So respond here and let me know what you think. I got a couple of replies on
the -dev list and they said that this would be good to put out on the -users
list too.
Mark Michelson
In true Republican fashion, I'm going to vote for case-insensitivity.
Given
On 10/1/2012 4:15 PM, Mark Michelson wrote:
Hi!
I've been confronted with an interesting issue to resolve. The
issue is located here:
https://issues.asterisk.org/jira/browse/ASTERISK-20163
The issue involves case-sensitivity of channel and global variables
in the dialplan. Current
- Original Message -
From: Vladimir Mikhelson v...@mikhelson.com
To: Asterisk Users Mailing List - Non-Commercial Discussion
asterisk-users@lists.digium.com
Sent: Tuesday, October 2, 2012 9:02:18 PM
Subject: Re: [asterisk-users] Case-sensitivity of Dialplan variables.
On 10/1
On Mon, Oct 1, 2012 at 4:15 PM, Mark Michelson mmichel...@digium.comwrote:
Hi!
I've been confronted with an interesting issue to resolve. The
issue is located here:
snip
So respond here and let me know what you think. I got a couple of replies
on the -dev list and they said that this
- 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
On 10/2/2012 9:12 PM, Warren Selby wrote:
On Mon, Oct 1, 2012 at 4:15 PM, Mark Michelson mmichel...@digium.com
mailto:mmichel...@digium.com wrote:
Hi!
I've been confronted with an interesting issue to resolve. The
issue is located here:
snip
So respond here and let
2012/10/1 Mark Michelson mmichel...@digium.com
Hi!
I've been confronted with an interesting issue to resolve. The
issue is located here:
https://issues.asterisk.org/**jira/browse/ASTERISK-20163https://issues.asterisk.org/jira/browse/ASTERISK-20163
The issue involves case-sensitivity of
Hi!
I've been confronted with an interesting issue to resolve. The
issue is located here:
https://issues.asterisk.org/jira/browse/ASTERISK-20163
The issue involves case-sensitivity of channel and global variables
in the dialplan. Current behavior is as follows:
1) Variables created in the
-Original Message-
From: asterisk-users-boun...@lists.digium.com
[mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Mark Michelson
Sent: Monday, October 01, 2012 4:15 PM
To: asterisk-users@lists.digium.com
Subject: [asterisk-users] Case-sensitivity of Dialplan variables.
Hi
On 10/1/2012 5:15 PM, Mark Michelson wrote:
(HASH would be evaluated properly but hash would not). My personal
opinion is that all variable evaluations should be case-sensitive.
+1
case insensitivity to accommodate carelessness is evil. much easier for
NoOp to tell us SIP_CODEC is unset,
23 matches
Mail list logo
