[asterisk-dev] Comments in extensions.conf with 2 dashes behind semicolon not being ignored when parsed?

[Tzafrir Cohen]

On Wed, May 28, 2008 at 03:56:44PM -0500, JR Richardson wrote:
> Hi All,
> 
> I use allot of comments throughout my config files, as I suspect most
> people do.  I just happened on a situation where a comment crashed my
> dial plan.  Here is the example in extensions.conf:
> 
> ;-some comment (1 dash)
> works, ignored
> 
> ;--some comment (2 dashes)
> get a parse error at the CLI:
> 
> lab11*CLI> dialplan reload
>   == Parsing '/etc/asterisk/extensions.conf':   == Found
> [May 28 14:43:17] WARNING[29502]: config.c:1392 config_text_file_load:
> Unterminated comment detected beginning on line 10
> 
> ;--some comment--; (2 dashes, close with semicolon)
> works, ignored
> 
> ;---some comment (3 or more dashes)
> works, ignored

> I'm wondering if this behavior can be corrected?  This behavior
> appears in 1.2 and 1.6.

Also documented even in 1.2:

http://svn.digium.com/svn/asterisk/branches/1.2/doc/README.configuration

-- 
               Tzafrir Cohen
icq#16849755              jabber:tzafrir.cohen at xorcom.com
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir