This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: [jjohnstn@cygnus.com: Re: cygwin/newlib types patchs]
- To: Robert Collins <robert dot collins at itdomain dot com dot au>
- Subject: Re: [jjohnstn@cygnus.com: Re: cygwin/newlib types patchs]
- From: Christopher Faylor <cgf at redhat dot com>
- Date: Tue, 27 Mar 2001 22:56:05 -0500
- Cc: cygwin-developers at cygwin dot com
- References: <EA18B9FA0FE4194AA2B4CDB91F73C0EF08EE94@itdomain002.itdomain.net.au>
- Reply-To: cygwin-developers at cygwin dot com
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)