From: Adam Christopher Lawrence <guruman AT interlog DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Headers, multiple .C files, and Allegro BITMAP structures.
Date: Sat, 26 Jul 1997 01:09:05 -0400
Organization: InterLog Internet Services
Lines: 20
Message-ID: <33D98670.58E49A34@interlog.com>
References: <33D8E413 DOT 16741DD1 AT interlog DOT com> <5ratj7$9pt AT news DOT ox DOT ac DOT uk>
NNTP-Posting-Host: ip213-162.cc.interlog.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

> Yes, the #include for allegro.h will take care of that when myprog.c
> is
> being compiled, but when iterator.c is being compiled (a seperate
> step)
> there is no #include for allegro.h. The most robust way to do this is
> to
> ensure that any header files that your header files requires are
> #included
> into your header file. Just add `#include <allegro.h>' to the start of
>
> iterator.h and all will be well. Don't worry about the allegro.h being
>
> included more than once (since it is included both directly into
> myprog.c
> and indirectly via iteratorh) because Shawn isn't stupid :) He's put
> precautions against this into his header file.

    Makes sense to me. Thanks!