DL>  Hello Mark!
 DL>
 DL>  15 Jun 96 15:22, Mark Kobussen wrote to All:
 DL>
 DL>   MK> report dozens and dozens of parsing errors. I'm using only ANSI C
 DL>   MK> functions, and it compiles fine on all of my other compilers.
 DL>
 DL>  What are some examples of code it's getting stuck on, and what are the
 DL>  errors it's reporting?

Well, I'll have to take another look at that. Don't really get much time to
see all the errors (they just fly by the screen), and I have the lucky
distinction of a keyboard with no Pause key. ;)

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

I'm pretty sure I used ONLY ANSI C functions, but I'm going to have to go
through and clean up the source.

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

Nope, didn't use FAR anywhere.

Thanks, I'm going to go look through my code and see if I put in non-ANSI C
calls anywhere.

Mark

...This copy of ProBoard has been unregistered for 90 days!

---  Binkley/FastEcho/ProBoard