[Spec-Chum]

Originally Posted by LooZee

Thank you.


Yes, that works. Of course, I expected that. But the point is, vbcc should compile with almost any C compiler, it's meant to be easily portable. As the thread starter's case and mine have shown, there is something about vbcc that some compilers don't get right - and there must be a reason for that.


For example, different compilers give different warnings. PellesC is pretty strict and gives dozens of warnings when compiling vbcc, and they're valid warnings about potentially uninitialized variables, comparing signed with unsigned numbers, unreachable code, unused data etc.


Good code is unambiguous and there are no two ways to interpret it. I'm trying to find the ambiguity in vbcc's code.

Ah, I see now, sorry.