Hello Mark!

15 Jun 96 15:22, Mark Kobussen wrote to All:

 MK> report dozens and dozens of parsing errors. I'm using only ANSI C
 MK> functions, and it compiles fine on all of my other compilers.

What are some examples of code it's getting stuck on, and what are the
errors it's reporting?

(It works fine for me.)

You might be trying to compile some code that has compiler specific
extensions, even though you're able to compile it on a number of compilers,
the code you're compiling may not be ANSI or POSIX compliant.

One such item is platform specific calls, platform specific calling
conventions.  Despite what many DOS programmers think, _far, __far, _FAR,
and FAR are not ANSI compliant.  They are DOS/OS2/WIN specific for 16-bit
segmented memory models.  It is an illegal keyword when writing 32-bit
code.

Daniel

--- GoldED/2 2.42.G0615+