Q related to this : When using,
QUIT TO my_file_spec.cmd is executed, it must surely (re-)open the file, "my_file_spec.cmd" and begin execution at the FIRST executable statement, as opposed to using RETURN, which would begin at the NEXT executable statement. Is this true? Thanks, Steve in Memphis > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On > Behalf Of A. Razzak Memon > Sent: Friday, July 05, 2002 3:04 PM > To: [EMAIL PROTECTED] > Subject: Re: Calculating Depth (FILE, not Personal Character) - Razzak's > Reply > > > > Steve, > > It depends on how many RUN statements you have! It looks like you > have too-many. > > When you use RUN filespec command from within a command or > procedure file, R:BASE adds one to the nesting level for each nested > command file. RETURN is the only way to exit command and to return > control to the next line in the calling command file, and the nesting > counter decreases by one. > > You can nest command files, such as RUN filespec, IF structures, > WHILE loops, and SWITCH structures. The number of control > structures that you can nest depends on the amount of memory > available when the command or procedure file executes. > > You can have up to five levels of RUN execution, unless you use the > SET FILES command to change the number of command files that > can be open simultaneously. In other words, command file 1 can > execute command file 2, command file 2 can execute command file 3, > command file 3 can execute command file 4, and command file 4 can > execute command file 5. Successive RETURN commands pass > execution control back up through the command files. > > It all comes down to defining nesting levels and ... making sure to return > control back to the originating command file. > > I recommend to use QUIT TO filespec command. > > Using the QUIT TO filespec command, there is no overhead, no nesting > level, nor does R:BASE have to keep track of nesting levels. > > Using the QUIT TO filespec command, you can QUIT TO any command > file at any level you wish and never have to worry about RETURNing to > the last command to return control to the one command before and so > on ... > > QUIT TO filespec command clears all nesting levels and resets the > nesting level to 0. Thus, no overhead. > > Hope that helps to understand the logic! > > Have a great weekend! > > Very Best Regards, > > Razzak. > > > At 02:03 PM 7/5/2002 -0500, J. Stephen Wills wrote: > > >As you might surmise, I'm having some problems. When I have FILE > >DEPTH = 5, I "lose" certain functionality, this functionality > being contained > >in the called file-modules. When I call them fm a "lower" > level, they work. > >Then I changed FILE DEPTH = 10, and re-ran the app "from the top" - well, > >bust my breeches, it worked. So, while I think I better understand the > >problem, I sure appreciate some input on the various/best ways to address > >it. > > > ================================================ > TO SEE MESSAGE POSTING GUIDELINES: > Send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: INTRO rbase-l > ================================================ > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: UNSUBSCRIBE rbase-l > ================================================ > TO SEARCH ARCHIVES: > http://www.mail-archive.com/rbase-l%40sonetmail.com/ > ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
