[asterisk-dev] Gosub and Macro

[Russell Bryant]

On May 26, 2008, at 12:25 PM, Atis Lezdins wrote:
> * create app_macro_wrapper which provides the same apps as app_macro
> but uses GoSub internally. This could be selected in menuselect by
> default to force new users use GoSub instead, but anybody could
> disable it and use old app_macro as before.

I would like to see this, as well.  However, Tilghman has indicated  
that writing a Macro implementation that uses GoSub internally would  
be extremely difficult, and perhaps impossible.  Perhaps he can  
comment some more on this.

> * ael parser could still generate macro-mymacro contexts without
> Return, so that macros can be called. However i see that then there
> would be troubles with accidentally having them mixed.
> * add option for AEL parser to not replace Macro with GoSub - for
> transitional period
> * issue big warning in UPGRADE.txt mentioning realtime. However this
> could create similar complains as it was recently with commas and
> pipes.

Does this issue really have anything to do with realtime?  I think the  
problem here is that any dialplan that works based on assumptions of  
how the AEL compiler works with respect to macros will be broken.   
This issue would exist for people calling a macro from extensions.conf  
that was implemented in extensions.ael.

I can't imagine that this is very common, and furthermore, I would  
like to strongly discourage making any assumptions about how AEL  
compiles into traditional Asterisk extensions.

--
Russell Bryant
Senior Software Engineer
Open Source Team Lead
Digium, Inc.