In Scunthorpe to see the BOS plant?
I am amazed but thinking about it I can not think of any other reason to come here.
Hope you did not travel far!
In Scunthorpe to see the BOS plant?
I am amazed but thinking about it I can not think of any other reason to come here.
Hope you did not travel far!
Steve Earl www.datageo.co.uk
Laughs...
Yes BOS Plant ..... Told if Really lucky might get to see your 4 Queens of steel making too....
Before dining in style at Deans on Brigg road !
Thanks for help again all
You saw the four queens!
I bet that made your day.
I assume Deans is a burger van.
You are welcome.
Steve Earl www.datageo.co.uk
Steve, I beg to differ about your statement:"Your if correct then labels construction can not be in one line format." Oh really, and what makes you say that? If the statement is TRUE the operation is passed to the address of Correct#. Although it is not the way I would write the compound statement it is 100% acceptable.
Dave Purola,
N8NTA
EN82fn
Dave you are correct as Henrik's post has already demonstrated. We both agree that we would not write the compound statement this way. My biggest objection is the use of the 'goto' statement which although perfectly valid is an instruction I was taught not to use a long time ago. I read the "Correct#" as a gosub instruction not a goto statement which was my mistake.
Steve Earl www.datageo.co.uk
It is typically necessary to use parenthesis between logical comparisons as:
If (Serial[1]=$15) and (Serial[2]=$D3) and (Serial[3]=$7D) AND (Serial[4]=$16) AND (Serial[5]=$00) AND (Serial[6]=$00) then correct1
I believe that it forces a Boolean comparison rather than a mathematical evaluation.
One last - is it necessary to compare ALL bytes, or might you only compare say... the first one. This would seem to yield a unique condition and save the effort and complexity of so long a line:
If (Serial[1]=$15) then Correct1
Bookmarks