Summary:ASTERISK-10097: conf2ael improvements
Reporter:Michiel van Baak (mvanbaak)Labels:
Date Opened:2007-08-16 13:47:30Date Closed:2011-06-07 14:08:13
Versions:Frequency of
Environment:Attachments:( 0) conf2ael_hinst.diff
( 1) conf2ael_wrong_newlines.diff
Description:conf2ael is very basic and misses loads of functionality.
This issue is to track patches against it to make it more beautiful
Comments:By: Steve Murphy (murf) 2007-08-16 14:31:21

Changes presented in conf2ael.hinst.diff were merged into trunk in 79736.
Many thanks to mvanbaak for his contribution!

I will keep this bug open so we have a place to attach contributions.
And a place to ridicule, laugh at, complain, suggest, compliment, whatever needs to be said. Please confine comments to conf2ael, and keep the language clean! :)

By: Michiel van Baak (mvanbaak) 2007-08-16 16:15:02

new patch to remove the newline after a => for an extension
That way we get output that might work :)

By: Steve Murphy (murf) 2007-08-21 13:37:40

I don't understand; the AEL compiler pretty much ignores whitespace (except as a token separator). It's really only significant in "words", which are handed to the ${} and $[] parsers as-is, and what's inside app call args are also handed over without mods. And $[] expressions are OK to have all the whitespace they want, also, including newlines.

Extensions.conf is not so tolerant of newlines, but this is not extensions.conf.

Newlines after or before => should be ignored. Are you seeing other behavior?

By: Joshua C. Colp (jcolp) 2007-12-18 09:57:11.000-0600

Nudge nudge poke poke.

By: Steve Murphy (murf) 2007-12-21 13:47:15.000-0600

Well, what I'm going to do is take this bug off the active list, and if anyone would like to file some code or bugs against conf2ael, they are more than welcome to reopen this issue, or to file a brand new one.

This way, this bug isn't inflating the number of open bugs.