CBFalconer said:
Obviously lcc-win32 is not able to compile legitimate portable C
code. I suggest complaining to the vendor. Jacob Navia reads this
newsgroup.
It appears (though I can't actually confirm this directly) that
lcc-win's library defines, in violation of the standard, a number of
identifiers that should be available to user programs.
The number of programs posted here recently that illustrate this kind
of problem is, shall we say, interesting. It's tempting to suspect
that some of the posters might be deliberately posting such examples
that they already know are mishandled by lcc-win.
Certainly lcc-win has some bugs (as does virtually all software), and
certainly such bugs should be reported, but comp.lang.c is not the
place for lcc-win bug reports. Post to comp.compilers.lcc or contact
jacob directly (or use whatever mechanism is suggested by lcc-win's
documentation).
If lcc-win rejects your program and you honestly don't know whether
the problem is in your program or in the implementation, then by all
means post here and we can help you with the language. But if (and I
emphasize *if*) your purpose is to publicize a bug rather than to
illuminate a C language issue, this isn't the place.