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 14:58:28 -0500 From: Christopher Faylor To: Christopher Faylor Subject: Re: current winsup/cygwin/*.h files policy Message-ID: <20001206145828.E9721@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: Christopher Faylor References: <15228862171 DOT 20001206222335 AT logos-m DOT ru> <20001206142931 DOT H8257 AT redhat DOT com> <030546333 DOT 20001206225140 AT logos-m DOT ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <030546333.20001206225140@logos-m.ru>; from deo@logos-m.ru on Wed, Dec 06, 2000 at 10:51:40PM +0300 On Wed, Dec 06, 2000 at 10:51:40PM +0300, Egor Duda wrote: >>>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. Hmm. You're right. I must have removed the multiple inheritence at some point. There is no reason not to use it, though. cgf