[asterisk-bugs] [Asterisk 0011937]: AelParse dump separates command parameters with pipes, that are not accepted by 1.6

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11937 
====================================================================== 
Reported By:                atis
Assigned To:                murf
====================================================================== 
Project:                    Asterisk
Issue ID:                   11937
Category:                   Utilities/aelparse
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.6.0-beta1 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             02-06-2008 05:10 CST
Last Modified:              02-11-2008 15:52 CST
====================================================================== 
Summary:                    AelParse dump separates command parameters with
pipes, that are not accepted by 1.6
Description: 
Processing the following command by aelparse
GoSub(db_dnis_routing,${EXTEN},1);

gives the following .conf file:

GoSub(db_dnis_routing|${EXTEN}|1)

This is valid for 1.4 (but obsolete) however this doesn't work on 1.6

It would be good idea to have aelparse separate command parameters by
commas also in 1.4 for compatibility.


====================================================================== 

---------------------------------------------------------------------- 
 murf - 02-11-08 15:52  
---------------------------------------------------------------------- 
I reviewed the code that generates the dump, and it looks OK;

If you have a problem in 1.4, please, supply me a short test AEL input
that
I can use, that would demonstrate a problem. Right now, if the output from
aelparse is acceptable to the extensions.conf parser, I would hesitate to
make even a cosmetic change... Maxims like these ring in my ears: "If it
works, don't fix it", and "Thou shalt not change release code, except for
really obvious, bad bugs that really need to be fixed." 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
02-11-08 15:52  murf           Note Added: 0082048                          
======================================================================