Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin-developers AT sources DOT redhat DOT com
Date:	Wed, 6 Dec 2000 14:29:31 -0500
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin-developers AT cygwin DOT com
Subject:	Re: current winsup/cygwin/*.h files policy
Message-ID:	<20001206142931.H8257@redhat.com>
Reply-To:	cygwin-developers AT cygwin DOT com
Mail-Followup-To:	cygwin-developers AT cygwin DOT com
References:	<15228862171 DOT 20001206222335 AT logos-m DOT ru>
Mime-Version:	1.0
User-Agent:	Mutt/1.3.11i
In-Reply-To:	<15228862171.20001206222335@logos-m.ru>; from deo@logos-m.ru on Wed, Dec 06, 2000 at 10:23:35PM +0300

On Wed, Dec 06, 2000 at 10:23:35PM +0300, Egor Duda wrote:
>Hi!
>
>  if   i  understand  correctly,  *.h  files  in  winsup/cygwin/  were
>redesigned   some  time  ago  from   single  monolithic  winsup.h to a
>bunch of small *.h files which don't use
>#ifndef _FOO_H_
>#define _FOO_H_
>...
>#endif
>construct,   and   should   be   included  in  *.cc  files  in correct
>order  to satisfy all dependencies.  there're,  however  4  *.h  files
>left,   which   include   other   "*.h"  files  --  heap.h,  pinfo.h,
>shared_info.h and winsup.h.  was it intentional?

Yes.  I'm not trying to be overly dogmatic about this.  If it makes sense
to include perthread.h in thread.h, then go ahead and do that.  Just make
sure that you remove any duplication from any source files.

>btw, does usage of c++'s multiple inheritance allowed in cygwin?

I'm not sure what you mean.  Aren't some fhandler classes doing this already?

cgf

- Raw text -