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 Date: Wed, 6 Dec 2000 22:51:40 +0300 From: Egor Duda X-Mailer: The Bat! (v1.45) Personal Reply-To: Egor Duda Organization: DEO X-Priority: 3 (Normal) Message-ID: <030546333.20001206225140@logos-m.ru> To: Christopher Faylor Subject: Re: current winsup/cygwin/*.h files policy In-reply-To: <20001206142931.H8257@redhat.com> References: <15228862171 DOT 20001206222335 AT logos-m DOT ru> <20001206142931 DOT H8257 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi! Wednesday, 06 December, 2000 Christopher Faylor cgf AT redhat DOT com wrote: >> 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? CF> Yes. I'm not trying to be overly dogmatic about this. If it makes sense CF> to include perthread.h in thread.h, then go ahead and do that. Just make CF> sure that you remove any duplication from any source files. ok. >>btw, does usage of c++'s multiple inheritance allowed in cygwin? CF> I'm not sure what you mean. Aren't some fhandler classes doing this already? no. 'grep "class.*:.*,.*" *' shows only lines in ChangeLogs. i was meaning that cygwin used to avoid some g++ features (-fno-exceptions -fno-rtti), so i wanted to make sure that multiple inheritance is ok in current gcc. Egor. mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19