From: Steve Murphy Date: Fri, 23 Mar 2007 15:57:26 +0000 (+0000) Subject: Added a few words in the Macro doc strings about the behavior of macros with hangups... X-Git-Tag: 1.2.18~58 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=fe9bbc5dfc1847eaa643975e33d88f5bc28b9934;p=thirdparty%2Fasterisk.git Added a few words in the Macro doc strings about the behavior of macros with hangups (et al.), as per 9337 git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.2@59186 65c4cc65-6c06-0410-ace0-fbb531ad65f3 --- diff --git a/apps/app_macro.c b/apps/app_macro.c index 425836278d..9835138f69 100644 --- a/apps/app_macro.c +++ b/apps/app_macro.c @@ -61,6 +61,11 @@ static char *descrip = "will be returned at the location of the Goto.\n" "If ${MACRO_OFFSET} is set at termination, Macro will attempt to continue\n" "at priority MACRO_OFFSET + N + 1 if such a step exists, and N + 1 otherwise.\n" +"Extensions: While a macro is being executed, it becomes the current context.\n" +" This means that if a hangup occurs, for instance, that the macro\n" +" will be searched for an "h" extension, NOT the context from which\n" +" the macro was called. So, make sure to define all appropriate\n" +" extensions in your macro! (you can use 'catch' in AEL) \n" "WARNING: Because of the way Macro is implemented (it executes the priorities\n" " contained within it via sub-engine), and a fixed per-thread\n" " memory stack allowance, macros are limited to 7 levels\n"