Re: [foxboro] HLBL problem
- From: Jerry Hidahl <Jerry_Hidahl@xxxxxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Fri, 2 Jan 2009 11:47:06 -0600
>Along with some of the other suggestions, I have experienced problems with
>labels when they exist near comments.
>For example:
>(* operator comment *)
><<quit>>
>
>I have had strange compile errors because of things like this. Typically
>we aren't worried about operator comments, so if you change the comment to
>a C style comment, the problem will go away.
>
>/* operator comment */
><<quit>>
I've been bit by this same problem a couple times and puzzled over it. The
key is the location of a label like <<quit>> or $$quit$$ must be at the
beginning of the line. A HLBL comment like (* operator comment *) are on
the same line as the label that follows it. Adding a semicolon after the
comment and before the label would fix it. Precompiler comments like /*
operator comment */ don't even get to the compiler, so they are really
skipped. As long as there's a semicolon before the label and nothing but
<LF> or space characters in-between, the label will work.
I've been bit by <CR> characters, too, because I always use Word for my
editing. I usually get a different syntax error when that happens. Use the
"Save As" option and make sure to specify the file type as plain text,
US-ASCII coding, check the "Insert line breaks" option, and End lines with
"LF-only". (All of this is just to avoid using VI editor.)
I think I've been bit by the missing close-comment character ( } ), too,
and it's a tough one to find.
Dirk, you're a fine man for locating and correcting this problem for your
colleague.
Jerry Hidahl
Process Control Engineer
Port Neches Performance Products
Huntsman Corporation
steve.shimp@exxon
mobil.com
Sent by: To
foxboro-bounce@fr foxboro@xxxxxxxxxxxxx
eelists.org cc
Subject
12/23/2008 10:29 Re: [foxboro] HLBL problem
AM
Please respond to
foxboro@freelists
.org
Along with some of the other suggestions, I have experienced problems with
labels when they exist near comments.
For example:
(* operator comment *)
<<quit>>
I have had strange compile errors because of things like this. Typically
we aren't worried about operator comments, so if you change the comment to
a C style comment, the problem will go away.
/* operator comment */
<<quit>>
Steve
foxboro-bounce@xxxxxxxxxxxxx wrote on 12/23/2008 10:00:47 AM:
>
> Hi list,
>
> I have a strange problem with a smal IND sequence. The code has been used
> unchanged for a long time. My collegue added a " WAIT 1;" and got a
compile
> error:
> #ERROR : label 'quit3' not declared
>
> #ERROR : label 'quit' not declared
>
> #ERROR : label 'quit2' not declared
>
> These three labels have been part of the code from the beginning and the
> code was compiled without errors long time ago. Now all of a sudden the
> labels (ie <<quit>>) ,which have not been changed, are causing a problem?
> I've retyped the label name and have checked all of the references to the
> labels but cannot find anything wrong. Any one experienced a similar
> problem?
>
> Thanks & Rgds
>
> Dirk Pauwels - DCS/MOC coordinator
> Engineering dept.
> Hexion Specialty Chemicals
> E mail: dirk.pauwels@xxxxxxxxxx
> T. +32.(0)3.570.95.97
> F. +32.(0)3.570.16.09
> Mob. +32.(0)497.428.300
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
