> yes, I had the hex dump at the end of the compile listing also.
> Interesting!

In my experience, that almost always means a bad relative branch target.
It should be the very first thing you look for in such cases.

Also, once in a great while, you'll come up with source that appears to
have nothing wrong with it, and yet it blows up the compiler; simply
changing the order of the last statement or two you added will usually
allow it to compile. Can't remember whether I've seen it in MI, or RPG, or
Java, or some old DOS development tools, but I know I've seen it
somewhere. It happens, without apparent reason, apparently the result of
something somehow overloading the parser.

--
JHHL



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.