[asterisk-bugs] [Asterisk 0010787]: Impossible to make optional macro arguments in 1.4

[noreply at bugs.digium.com]

The following issue has been CLOSED 
====================================================================== 
http://bugs.digium.com/view.php?id=10787 
====================================================================== 
Reported By:                Luke-Jr
Assigned To:                murf
====================================================================== 
Project:                    Asterisk
Issue ID:                   10787
Category:                   PBX/pbx_ael
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     closed
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:              
Resolution:                 open
Fixed in Version:           
====================================================================== 
Date Submitted:             09-21-2007 04:49 CDT
Last Modified:              10-03-2007 13:09 CDT
====================================================================== 
Summary:                    Impossible to make optional macro arguments in 1.4
Description: 
In 1.2, AEL didn't validate macro argument counts, and all was well. Now
AEL errors if they don't have the same number, which means macros are
forced to have a fixed number of arguments ?
====================================================================== 

---------------------------------------------------------------------- 
 murf - 10-03-07 13:09  
---------------------------------------------------------------------- 
Yes, sorry; but the emphasis on AEL2 was safety. And one common error in
all procedural languages is mucking up the arglists in function calls.

since everything is strings in AEL, I can't really do any argument type
checking, but at least we can help make sure the arg count is correct.

Things on my list for the future are stuff like letting macros return a
value, and maybe we can slide in some default values for macro args... if
you really feel strongly about this sort of thing, you might open a new bug
report and ask for the feature as an enhancement request. I'll then be able
to schedule it to some degree. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-03-07 13:09  murf           Note Added: 0071402                          
======================================================================