Mail Archives: djgpp/1996/10/10/16:23:30
Date: | Thu, 10 Oct 1996 16:02:22 -0400 (EDT)
|
From: | James Flemer <flemer AT panther DOT middlebury DOT edu>
|
To: | djgpp mailing list <djgpp AT delorie DOT com>
|
Subject: | Re: Error using allegro. (maybe)
|
In-Reply-To: | <Pine.SUN.3.91.961010092747.10390O-100000@is>
|
Message-Id: | <Pine.A32.3.95.961010155302.89734A-100000@panther.middlebury.edu>
|
Mime-Version: | 1.0
|
On Thu, 10 Oct 1996, Eli Zaretskii wrote:
>
> On Wed, 9 Oct 1996, James Flemer wrote:
>
> > includes 'allegro.h'. I have included all the info I thought relavant
>
> "foo.h" is certainly relevant, but you didn't include it. What happens
> if you move #include "foo.h" *after* allegro.h?
>
-- SNIP --
Thanks, but it was a stupid mistake I made, and I don't believe I did not
see it before. I had a typo in 'foo.h' in my define for TRUE, and the
allegro.h file uses #ifndef TRUE, and therefor did not change my
definition. The other module compiled because 'allegro.h' was included
before 'foo.h' like you mentioned.
Thanks anyway.
- James Flemer
<flemer AT panther DOT middlebury DOT edu>
- Raw text -