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: Tue, 27 Mar 2001 22:56:05 -0500 From: Christopher Faylor To: Robert Collins Cc: cygwin-developers AT cygwin DOT com Subject: Re: [jjohnstn AT cygnus DOT com: Re: cygwin/newlib types patchs] Message-ID: <20010327225605.B29339@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: Robert Collins , cygwin-developers AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: ; from robert.collins@itdomain.com.au on Wed, Mar 28, 2001 at 01:46:15PM +1000 On Wed, Mar 28, 2001 at 01:46:15PM +1000, Robert Collins wrote: >> What is cygwin-dependent? Doesn't it make sense to keep everything in >> one place, even if you have to "#ifdef __CYGWIN__"? > >No. The cygwin-classes and internals aren't newlib specific. The >external interfaces are newlib-specific. As an example, if Mumit picks >up his glibc port, the cygwin-classes will stay the same, but the glibc >externals will be needed. Hopefully those external interfaces are posix >standard and there's no difference :] Can you give me an example? cgf (Btw, I've redirected this to cygwin-developers)