Yes sir, thank you John.
In my notes I had written *{} as being the format...on further thinking I
suppose that the * would just be wild cards when checking the code.
Again thank you, hope you and yours are having a great week.
tom
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of John Minyo
II
Sent: Monday, November 09, 2009 2:54 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: Unknown Entry/Exit Procedure Error
At 02:23 PM 11/9/2009, you wrote:
>I thought you had to use *{} --- should it just be {} because I do see that
>if I remove the comments the error vanishes....but it is not picked up in
>code check and it is how I have been commenting since I heard it was
>possible to include parends in that manner.
Hello Tom,
R:BASE actually supports three variations of commented lines in command
files;
the double hyphens "--", the open and close braces "{ }", and the
open and close
parenthesis preceded by an asterisk "*( )".
A "--" comment can be used only on a single line either by itself or
following
a command.
A "{ }" comment may share a command line with a command, occupy a line
itself,
or extend over multiple command lines. This designator is the
recommended option
with the latest releases of R:BASE, as if helps in avoiding any confusion
when
using parentheses with your R:BASE expressions. The set of braces
"{}", with the
desired commented text or commands enclosed within the braces will comment
the
text.
A "*( )" comment may share a command line with a command, occupy a
line itself,
or extend over multiple command lines. R:BASE interprets text
following an asterisk
and left parenthesis as a comment until a closing right parenthesis
is reached.
Although this option is still supported in R:BASE, it is now
recommended that you
use the braces "{}" method above.
Keep in mind that any command(s) that is embedded within a
multiple-line comment
will not be executed.
So, in your EEP, the asterisk in front of the braces was causing the error.
John
