You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Steve Murphy 4c7393a6a4 closes issue #11086 where a user complains that references to following contexts report a problem; The problem was REALLy that he was referring to empty contexts, which were being ignored. Reporter stated that empty contexts should be OK. I checked it out against extensions.conf, and sure enough, empty contexts ARE ok. So, I removed the restriction from AEL. This, though, highlighted a problem with multiple contexts of the same name. This should be OK, also. So, I added the extend keyword to AEL, and it can preceed the 'context' keyword (mixed with 'abstract', if nec.). This will turn off the warnings in AEL if the same context name is used 2 or more times. Also, I now call ast_context_find_or_create for contexts now, instead of just ast_context_create; I did this because pbx_config does this. The 'extend' keyword thus becomes a statement of intent. AEL can now duplicate the behavior of pbx_config, ... git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.4@87168 65c4cc65-6c06-0410-ace0-fbb531ad65f3		18 years ago
..
ael-ntest9	OK, here is everything I changed to fix 7474:	20 years ago
ael-ntest10	The contents of branch teams/murf/bug_7598 are being folded in here.	20 years ago
ael-ntest12	This branch will resolve the bug 7635.	20 years ago
ael-ntest22	This is a regression update that matches what I did in 84134 for AEL regressions.	18 years ago
ael-test1	This commit merges the contents of 7721, as it applied to the trunk version. Added the item that would previously trigger a false error to test1.	19 years ago
ael-test2	Merge Steve Murphy's (murf) complete re-implementation of AEL, which is now no longer considered experimental :-)	20 years ago
ael-test3	This commit is a basic AEL enhancement: c-style comments	19 years ago
ael-test4	Merge Steve Murphy's (murf) complete re-implementation of AEL, which is now no longer considered experimental :-)	20 years ago
ael-test5	Merge Steve Murphy's (murf) complete re-implementation of AEL, which is now no longer considered experimental :-)	20 years ago
ael-test6	Merge Steve Murphy's (murf) complete re-implementation of AEL, which is now no longer considered experimental :-)	20 years ago
ael-test7	Merge Steve Murphy's (murf) complete re-implementation of AEL, which is now no longer considered experimental :-)	20 years ago
ael-test8	merge changes from team/murf/AEL-trunk-fixesonly	20 years ago
ael-test11	The contents of branch teams/murf/bug_7598 are being folded in here.	20 years ago
ael-test14	Changes to fix all problems reported in 7804 are included here.	19 years ago
ael-test15	This commit is a basic AEL enhancement: c-style comments	19 years ago
ael-test16	These changes fix the problems reported in bug 8090	19 years ago
ael-test18	updated the ael regressions to match what's in trunk	19 years ago
ael-test19	updated the ael regressions to match what's in trunk	19 years ago
ael-test20	updated the ael regressions to match what's in trunk	19 years ago
ael-vtest13	This bug adds enhancement as per bug 7606, the -w	20 years ago
ael-vtest17	Bug 8128 fixed in this release via these changes	19 years ago
ael-vtest21	This patch fixes bug 10411. I added a new regression test, some regression test cleanups	18 years ago
ref.ael-ntest9	These changes fix the problems reported in bug 8090	19 years ago
ref.ael-ntest10	closes issue #10834 ; where a null input to a switch statement results in a hangup; since switch is implemented with extensions, and the default case is implemented with a '.', and the '.' matches 1 or more remaining characters, the case where 0 characters exist isn't matched, and the extension isn't matched, and the goto fails, and a hangup occurs. Now, when a default case is generated, it also generates a single fixed extension that will match a null input. That extension just does a goto to the default extension for that switch. I played with an alternate solution, where I just tack an extra char onto all the patterns and the goto, but not the default case's pattern. Then even a null input will still have at least one char in it. But it made me nervous, having that extra char in , even if that's a pretty secret and low-level issue.	18 years ago
ref.ael-ntest12	These changes fix the problems reported in bug 8090	19 years ago
ref.ael-ntest22	This is a regression update that matches what I did in 84134 for AEL regressions.	18 years ago
ref.ael-test1	closes issue #10834 ; where a null input to a switch statement results in a hangup; since switch is implemented with extensions, and the default case is implemented with a '.', and the '.' matches 1 or more remaining characters, the case where 0 characters exist isn't matched, and the extension isn't matched, and the goto fails, and a hangup occurs. Now, when a default case is generated, it also generates a single fixed extension that will match a null input. That extension just does a goto to the default extension for that switch. I played with an alternate solution, where I just tack an extra char onto all the patterns and the goto, but not the default case's pattern. Then even a null input will still have at least one char in it. But it made me nervous, having that extra char in , even if that's a pretty secret and low-level issue.	18 years ago
ref.ael-test2	This is a regression update that matches what I did in 84134 for AEL regressions.	18 years ago
ref.ael-test3	closes issue #10834 ; where a null input to a switch statement results in a hangup; since switch is implemented with extensions, and the default case is implemented with a '.', and the '.' matches 1 or more remaining characters, the case where 0 characters exist isn't matched, and the extension isn't matched, and the goto fails, and a hangup occurs. Now, when a default case is generated, it also generates a single fixed extension that will match a null input. That extension just does a goto to the default extension for that switch. I played with an alternate solution, where I just tack an extra char onto all the patterns and the goto, but not the default case's pattern. Then even a null input will still have at least one char in it. But it made me nervous, having that extra char in , even if that's a pretty secret and low-level issue.	18 years ago
ref.ael-test4	This is a regression update that matches what I did in 84134 for AEL regressions.	18 years ago
ref.ael-test5	closes issue #10834 ; where a null input to a switch statement results in a hangup; since switch is implemented with extensions, and the default case is implemented with a '.', and the '.' matches 1 or more remaining characters, the case where 0 characters exist isn't matched, and the extension isn't matched, and the goto fails, and a hangup occurs. Now, when a default case is generated, it also generates a single fixed extension that will match a null input. That extension just does a goto to the default extension for that switch. I played with an alternate solution, where I just tack an extra char onto all the patterns and the goto, but not the default case's pattern. Then even a null input will still have at least one char in it. But it made me nervous, having that extra char in , even if that's a pretty secret and low-level issue.	18 years ago
ref.ael-test6	backport of 80649, a fix to an unreported problem in the ael parser, that results in a crash on a 64bit machine	18 years ago
ref.ael-test7	These mods fix bug 9623, where an '@' in the eswitch contents causes a syntax error. I also updated the regressions.	19 years ago
ref.ael-test8	closes issue #10834 ; where a null input to a switch statement results in a hangup; since switch is implemented with extensions, and the default case is implemented with a '.', and the '.' matches 1 or more remaining characters, the case where 0 characters exist isn't matched, and the extension isn't matched, and the goto fails, and a hangup occurs. Now, when a default case is generated, it also generates a single fixed extension that will match a null input. That extension just does a goto to the default extension for that switch. I played with an alternate solution, where I just tack an extra char onto all the patterns and the goto, but not the default case's pattern. Then even a null input will still have at least one char in it. But it made me nervous, having that extra char in , even if that's a pretty secret and low-level issue.	18 years ago
ref.ael-test11	This patch fixes bug 10411. I added a new regression test, some regression test cleanups	18 years ago
ref.ael-test14	This patch fixes bug 10411. I added a new regression test, some regression test cleanups	18 years ago
ref.ael-test15	These changes fix the problems reported in bug 8090	19 years ago
ref.ael-test16	closes issue #11086 where a user complains that references to following contexts report a problem; The problem was REALLy that he was referring to empty contexts, which were being ignored. Reporter stated that empty contexts should be OK. I checked it out against extensions.conf, and sure enough, empty contexts ARE ok. So, I removed the restriction from AEL. This, though, highlighted a problem with multiple contexts of the same name. This should be OK, also. So, I added the extend keyword to AEL, and it can preceed the 'context' keyword (mixed with 'abstract', if nec.). This will turn off the warnings in AEL if the same context name is used 2 or more times. Also, I now call ast_context_find_or_create for contexts now, instead of just ast_context_create; I did this because pbx_config does this. The 'extend' keyword thus becomes a statement of intent. AEL can now duplicate the behavior of pbx_config,	18 years ago
ref.ael-test18	closes issue #10834 ; where a null input to a switch statement results in a hangup; since switch is implemented with extensions, and the default case is implemented with a '.', and the '.' matches 1 or more remaining characters, the case where 0 characters exist isn't matched, and the extension isn't matched, and the goto fails, and a hangup occurs. Now, when a default case is generated, it also generates a single fixed extension that will match a null input. That extension just does a goto to the default extension for that switch. I played with an alternate solution, where I just tack an extra char onto all the patterns and the goto, but not the default case's pattern. Then even a null input will still have at least one char in it. But it made me nervous, having that extra char in , even if that's a pretty secret and low-level issue.	18 years ago
ref.ael-test19	closes issue #11086 where a user complains that references to following contexts report a problem; The problem was REALLy that he was referring to empty contexts, which were being ignored. Reporter stated that empty contexts should be OK. I checked it out against extensions.conf, and sure enough, empty contexts ARE ok. So, I removed the restriction from AEL. This, though, highlighted a problem with multiple contexts of the same name. This should be OK, also. So, I added the extend keyword to AEL, and it can preceed the 'context' keyword (mixed with 'abstract', if nec.). This will turn off the warnings in AEL if the same context name is used 2 or more times. Also, I now call ast_context_find_or_create for contexts now, instead of just ast_context_create; I did this because pbx_config does this. The 'extend' keyword thus becomes a statement of intent. AEL can now duplicate the behavior of pbx_config,	18 years ago
ref.ael-test20	updated the ael regressions to match what's in trunk	19 years ago
ref.ael-vtest13	closes issue #10834 ; where a null input to a switch statement results in a hangup; since switch is implemented with extensions, and the default case is implemented with a '.', and the '.' matches 1 or more remaining characters, the case where 0 characters exist isn't matched, and the extension isn't matched, and the goto fails, and a hangup occurs. Now, when a default case is generated, it also generates a single fixed extension that will match a null input. That extension just does a goto to the default extension for that switch. I played with an alternate solution, where I just tack an extra char onto all the patterns and the goto, but not the default case's pattern. Then even a null input will still have at least one char in it. But it made me nervous, having that extra char in , even if that's a pretty secret and low-level issue.	18 years ago
ref.ael-vtest17	closes issue #10834 ; where a null input to a switch statement results in a hangup; since switch is implemented with extensions, and the default case is implemented with a '.', and the '.' matches 1 or more remaining characters, the case where 0 characters exist isn't matched, and the extension isn't matched, and the goto fails, and a hangup occurs. Now, when a default case is generated, it also generates a single fixed extension that will match a null input. That extension just does a goto to the default extension for that switch. I played with an alternate solution, where I just tack an extra char onto all the patterns and the goto, but not the default case's pattern. Then even a null input will still have at least one char in it. But it made me nervous, having that extra char in , even if that's a pretty secret and low-level issue.	18 years ago
ref.ael-vtest21	This patch fixes bug 10411. I added a new regression test, some regression test cleanups	18 years ago
runtests	This bug adds enhancement as per bug 7606, the -w	20 years ago
setref	Merge Steve Murphy's (murf) complete re-implementation of AEL, which is now no longer considered experimental :-)	20 years ago