Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com From: Chris Faylor Date: Tue, 22 Aug 2000 12:10:46 -0400 To: cygwin-developers AT sources DOT redhat DOT com Subject: Re: Eliminating monolithic winsup.h Message-ID: <20000822121046.E28173@cygnus.com> Reply-To: cygwin-developers AT sources DOT redhat DOT com Mail-Followup-To: cygwin-developers AT sources DOT redhat DOT com References: <20000822121225 DOT 16018 DOT qmail AT web115 DOT yahoomail DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i In-Reply-To: <20000822121225.16018.qmail@web115.yahoomail.com>; from earnie_boyd@yahoo.com on Tue, Aug 22, 2000 at 05:12:25AM -0700 On Tue, Aug 22, 2000 at 05:12:25AM -0700, Earnie Boyd wrote: >--- Chris Faylor wrote: >> >> One thing that I'm not 100% sure about is relying on header file ordering. >> Currently, I've tried to keep everything flat. That means that .h files do >> not include other .h files even if they depend on them. >> > >Won't that make it harder to determine dependencies? So if I have header b.h >that requires header a.h and I don't #include within b.h then how do I >determine dependencies? The header files don't have dependencies, the .cc and .c files do. cgf