Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Mon, 6 Jun 2005 11:33:11 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Serious performance problems (malloc related?)
Message-ID:	<20050606093311.GE3268@calimero.vinschen.de>
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<3D848382FB72E249812901444C6BDB1D03E04FD3 AT exchange DOT timesys DOT com> <20050602190022 DOT GG6597 AT trixie DOT casa DOT cgf DOT cx>
Mime-Version:	1.0
In-Reply-To:	<20050602190022.GG6597@trixie.casa.cgf.cx>
User-Agent:	Mutt/1.4.2i

On Jun  2 15:00, Christopher Faylor wrote:
> You could do things the other way around, so that NtCreateFile is used
> in the main code which invokes a NtCreateFile wrapper for 9x systems but
> I am leery of doing things this way since that means that the only
> people capable of writing code for cygwin are the people who understand
> Nt* calls.  That is a subset of the already small number of people who
> understand the UNIX and Windows APIs well enough to work on Cygwin.

I don't see this as such a big problem.  The Nt calls are not used all
over the place and they are not needed all over the place.  Using them
carefully and in a well documented manner should keep it pretty simple
to follow.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -