This is the mail archive of the
mailing list for the cygwin project.
Re: Serious performance problems (malloc related?)
- From: Christopher Faylor <cgf-no-personal-reply-please at cygwin dot com>
- To: The Cygwin-Talk Maligning List <cygwin-talk at cygwin dot com>
- Date: Thu, 2 Jun 2005 15:50:48 -0400
- Subject: Re: Serious performance problems (malloc related?)
- References: <3D848382FB72E249812901444C6BDB1D03E04FD3@exchange.timesys.com> <20050602190022.GG6597@trixie.casa.cgf.cx> <firstname.lastname@example.org>
- Reply-to: The Cygwin-Talk Maligning List <cygwin-talk at cygwin dot com>
- Reply-to: cygwin-talk at cygwin dot com
On Thu, Jun 02, 2005 at 12:39:17PM -0700, Shankar Unni wrote:
>Christopher Faylor wrote:
>>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.
>You mean, like 2? (Err, 3. I mean, 4, or maybe 5..)
>I'm not sure this is a huge problem, you know..
Just take a look at the number of people who have contributed to
cygwin-patches in the last year or so. I wouldn't want to scare away
the people who contribute trivial patches because they can't find any
documentation on "NtCreateFile".
I suppose *we* could produce documentation on the Nt* functions but
that's also a support burden.
OTOH, "leery" doesn't mean "it will never happen". This is just one
of many things to consider when making a major change like this.