Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!snorkelwacker!bloom-beacon!eru!luth!sunic!mcsun!unido!pbinfo-n!mh
From: mh@uni-paderborn.de (Martin Husemann)
Newsgroups: comp.lang.c
Subject: Re: Syntax errors in include files????
Message-ID: <1990May9.112710.2868@uni-paderborn.de>
Date: 9 May 90 11:27:10 GMT
References: <222@dynasys.UUCP> <1990May2.152425.24723@druid.uucp> <921@emdeng.Dayton.NCR.COM>
Organization: Uni-GH Paderborn, West Germany
Lines: 36

btrue@emdeng.Dayton.NCR.COM (Barry.True) writes:

>In article <1990May2.152425.24723@druid.uucp> darcy@druid.UUCP (D'Arcy J.M. Cain) writes:
>>In article <222@dynasys.UUCP> jessea@dynasys.UUCP () writes:
>>>I'm getting all kinds of syntax errors from include files when I try
>>>to compile stuff - like times.h, types.h.  Can anyone tell me why
>>>I'm getting syntax errors from my include files?  I haven't done any

>You also may have other include files which need to be included before
>these. Since you haven't given much information about what specific things
>the compiler is complaining about I can't give you much more help. You
>might want to check your programmers reference manual if you have one
>handy.

It happend to me when I started using Turbo-C. I called Borland and
they didn't know about any problems. I sent them my source code, and
configuration/project files. They replied: don't use the option "ANSI 
keywords only" when compiling with <dos.h>. It defines some functions
of type "interrupt", which, obviously, isn't an ansi keyword.

I then hacked up my include files to say 
# ifdef __STD_C__
# define interrupt /***/
# endif

It worked fine, also I think, Borland should have done this before
delivering the headers. It wasn't mentioned in the manual ;-) so RTFM
didn't help me much.

I conclude, that programming DOS isn't ANSI-compliant.

-- 

Martin Husemann
mh@uni-paderborn.de
...!uunet!unido!pbinfo!mh