ftp.delorie.com/archives/browse.cgi | search |
From: | "Tony O'Bryan" <aho450s AT nic DOT smsu DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: rhide and djgpp |
Date: | Fri, 12 Dec 1997 07:06:08 -0600 |
Organization: | Southwest Missouri State University |
Lines: | 12 |
Message-ID: | <349136C0.25F5@nic.smsu.edu> |
References: | <3490A9AE DOT 633190F8 AT uclink4 DOT berkeley DOT edu> |
Reply-To: | aho450s AT nic DOT smsu DOT edu |
NNTP-Posting-Host: | sara.a50.smsu.edu |
Mime-Version: | 1.0 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Paul Frank wrote: > > im using rhide with djgpp and im linking the allegro library in. at > what seems like random times, the compiler spits out "parse error"s on > lines of perfect c code. sometimes it works fine. sometimes it doesnt. > but lines like "int x;" shouldnt produce errors, or so ive been led to > think. anyone have similar problems or know what's up? There is one possibility I have encountered where my perfectly valid C code will generate a compile error when using Allegro. if <stdio.h> is included after <allegro.h> is included an EOF redefinition is reported. The solution is to include <stdio.h> before including <allegro.h>.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |