[asterisk-bugs] [Asterisk 0010642]: Config parser eats blank lines for dinner

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10642 
====================================================================== 
Reported By:                jsmith
Assigned To:                murf
====================================================================== 
Project:                    Asterisk
Issue ID:                   10642
Category:                   Core/ManagerInterface
Reproducibility:            always
Severity:                   minor
Priority:                   low
Status:                     assigned
Asterisk Version:           1.4.11  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             09-04-2007 14:02 CDT
Last Modified:              09-04-2007 15:34 CDT
====================================================================== 
Summary:                    Config parser eats blank lines for dinner
Description: 
The Asterisk config parser (that is used by AMI for GetConfig/UpdateConfig,
etc.) eats blank lines in the configuration files, which makes it harder
for people to read the configuration file after it's been edited by
Asterisk.

I've talked with murf about this, and he asked me to open a bug and assign
it to him.
====================================================================== 

---------------------------------------------------------------------- 
 bkruse - 09-04-07 15:34  
---------------------------------------------------------------------- 
Does this mean that when I am using updateconfig and getconfig that I can
possibly start sending comments also?

Also, will it be a lot of overhead to receive/send those ;comments and
blank lines?

Please keep me updated to see if I need to change the API. Now we just
have comment => whatever for context's in the dialplan, and they get
parsed.

However, I could make the GUI clean up the code, and make it MUCH more
editable and readable.

This could possibly lead to a perfect integration of creating things in
the GUI, and the user being able to edit them, as where now it its kind of
convoluted and obfuscated at points.

I like it.

-bk 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
09-04-07 15:34  bkruse         Note Added: 0069930                          
======================================================================