Jose's API Headers III 1.05

[José Roca]

It could be that he is using a combination of #INCLUDEs that it is crashing the compiler's parser. In my CSED editor, I had to change the order of the includes because the parser went mad and reported inexistent errors.

[David Kenny]

Jose,

Did that get reported and looked at by PB support?  I only ask because I think I remember you were a key beta tester.  At least, in your case, the compiler didn't crash.  Still a bug though.

Jim,

I agree with you and Jose that it could be "fixed" by moving things around.  I was merely pointing out that Dan has exposed a compiler bug(Jose is right that it is likely the parser routines) to encourage him report it to PB support.  Of course, Dan has to be comfortable allowing them to have access to this particular code.

[José Roca]

Did that get reported and looked at by PB support?  I only ask because I think I remember you were a key beta tester.  At least, in your case, the compiler didn't crash.  Still a bug though.

Indeed, but nothing was done. My guess is that the solution would be to increase the number of nested levels (currently 16) for conditional compilation statements. To worsen things, macros also count with regard to nested levels.

But if the compiler is unable to deal with the code, it should display an error pointing that some limit(s) have been reached, not to crash or behave erratically.