Fred, Your description is correct.
#EXITC will return to the previous section in the .tmp file call stack. #EXIT leaves .tmp file processing immediatly, flushing any pending conditional output and moves on to the next item in the code processing event list. For .tmp processing, if you had something like, @MYSEC1 (1.1) #CALL(MYSEC2) (1.2) @ @MYSEC2 (2.1) #IF(#myvar=1)<(2.2) #EXIT?> (2.3) @ where #EXIT? above can be either #EXIT or #EXITC For #myvar=0 and you use either #EXIT or #EXITC you should see (1.1) (2.1) (2.3) (1.2) For #myvar=1 and you use #EXIT you should see (1.1) (2.1) #EXIT tosses away the stuff inside any conditionals that it's contained in and exits .tmp file processing without returning control to @MYSEC1 For #myvar=1 and you use #EXITC you should see (1.1) (2.1) (2.2) (1.3) #EXITC retains any conditional info and returns output control to @MYSEC1 Please keep in mind that conditional contents are not flushed to the output stream until all conditionals are resolved as true. So if the calls into the above sections were nested inside another conditional and you had a #EXIT in that conditional something like #IF(#mycallflag=1)<#CALL(MYSEC1)#IF(#myretvar=1)<#EXIT>> and #myretvar does equal 1, then even though the nested #EXITC retained the info from MYSEC1 and 2 it would still all be tossed when it hit the #EXIT in the #myretvar test. If that's not enough to make your head hurt, I'm impressed! For conditional nesting, 6 deep means that within your .tmp processing you can stack up to 6 open condition levels (<). After 6, if the processor encounters a 7th it's an error. Example1: <#XPOS> when processing #XPOS the conditional level=1 Example2: #IF(#myvar=1)<#ZPOS <#XPOS>> when processing #ZPOS the conditional level=1 when processing #XPOS the conditional level=2 Have fun, --gregg "Lauzus, Frederick" wrote: > Thanks John. As always your help is greatly appreciated. > > After searching through the release notes,(a nice stroll down memory lane), > I found that the reference to #EXITC was in the "What's New" section of the > v11 help files and the "Whatsnew.txt" file on the V11 CD where it's stated > as follows... > > #CALL Stack Improvements include: > > 1. A new #EXITC command returns processing to the calling @section after > processing any pending conditionals. Also, the pending conditional > level > has been expanded from 3 deep to 6 deep. > > I assume #EXITC stands for "exit call". I also assume that when I nest > multiple call statements (up to 255), by using #EXITC processing will return > to the previous call in the stack while #EXIT will collapse the entire > stack. I still don't know what is meant by the phrase "after processing any > pending conditionals". > > I assume the statement "the pending conditional level has been expanded from > 3 deep to 6 deep" means I can either nest conditional expressions 6 deep or > have up to 6 multiple conditional tests in one expression. The code > generator guide doesn't specify the limits of either. > > I'll have to try them out and see what works. > > ============================================= > Fred Lauzus, CAM Programming Coordinator > High Steel Structures, Incorporated > mailto:[EMAIL PROTECTED] http://www.highsteel.com > ============================================= > > > -----Original Message----- > From: John Huston [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, April 05, 2000 10:54 AM > To: Lauzus, Frederick > Cc: SmartCAM Email Group > Subject: Re: [mfg-smartcam] #EXIT vs. #EXITC > > Fred, > > FYI - The old release notes are now available on the SDRC Web at: > http://www.sdrc.com/nav/support-training/product-updates/patches/patches.htm > l > > The file is: "scmrelnt.zip" (4,021,127 bytes) > > Look down towards the bottom of the page under "SmartCAM Technical > Information" > > Thanks, > <john> > > "Lauzus, Frederick" wrote: > > > Could someone explain the difference between the template words #EXIT and > > #EXITC ? I have used #EXIT in the past but am unfamiliar with it's newer > > companion. The text in the manual is of little help. > > > > #EXIT > > Description: Exits a section early. > > > > #EXITC > > Description: Returns processing to the calling @section > > after processing any pending conditionals. > > > > I believe there was mention of this in one of the release notes prior to > > v11, but I no longer have those. > > > > > > ============================================= > > Fred Lauzus, CAM Programming Coordinator > > High Steel Structures, Incorporated > > mailto:[EMAIL PROTECTED] http://www.highsteel.com > > ============================================= > > > > > > ====================================================================== > > To find out more about this mailing list including how to unsubscribe, > > send the message "info mfg-smartcam" to [EMAIL PROTECTED] > > ====================================================================== > > ====================================================================== > To find out more about this mailing list including how to unsubscribe, > send the message "info mfg-smartcam" to [EMAIL PROTECTED] > ====================================================================== > ====================================================================== > To find out more about this mailing list including how to unsubscribe, > send the message "info mfg-smartcam" to [EMAIL PROTECTED] > ====================================================================== -- Gregg Olson Development Manager SDRC CAM Products ====================================================================== To find out more about this mailing list including how to unsubscribe, send the message "info mfg-smartcam" to [EMAIL PROTECTED] ======================================================================
