Re: [foxboro] HLBL problem


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:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: