Posted by Bob A on February 07, 2011 at 09:25:28:
"Education is when you read the fine print; experience is what you get when you don't." ~Pete Seeger
The first problem, and the one that hid the other problems was unbalanced compile time directives:
.if DECPASS
.endif
.if EXEPASS
.ifdef
.endif
.ifdef
.endif
this seems to have caused the compiler to get lost somehow.... the good news is that this did not happen when Barbara compiled it which seems to indicate that when the current compilers get to the end of an INCLUDE file they POP the stack of the directives, so this is not a current problem
the second problem has to do with
1) I had coded BREAK statemtents inside a SELECT/ENDSELECT
2) the COMET wiki says:
"The BREAK statement transfers control to the statement following the ENDSELECT statement."
While BREAKS within SELECT/ENDSELECT are allowed today, with current MTB, this does not seem to be the case with Comet 2008/Build 391, since it generates
EXCP "27 BREAK or CONTINUE found, no FOR/DO"
seems that my MTB only knows about FOR/DO
The final problem, for which I have no explanation whatsoever was the interaction between the MTB compiler and the output of the compiler. For whatever reason, MTB chokes on one of the files I used as output of the compiler.... after I created a new file as output of the compiler, everything looks OK.... on one file only, no matter what I compile, there are multiple unprintable characters and the compile aborts... not sure why, but seems all I have to do is stay away from this file.
As the Danish Nobelist (and father of a Nobelist!) Niels Bohr said:
"An expert is a person who has made all the mistakes that can be made in a very narrow field."
Suddenly I feel much more Expert
In Conclusion Thanx to one and all for help! Not sure when I'll be able to return the favour!
Bob "A"
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.