From: "Trevor Forbes" <trevorforbes@ozemail.com.au>
To: "Cygwin" <cygwin@cygwin.com>
Subject: Re: Linking to cygwin1.dll and msvcrt.dll ?
Date: Sat, 21 Jul 2001 20:31:00 -0000 [thread overview]
Message-ID: <118b01c1125e$e4739390$0300a8c0@ufo> (raw)
In-Reply-To: <053201c11242$c07ddca0$806410ac@local>
>
> > I am not in a position to judge "creeping feature'ism". It is
> > just that these 4 *ex methods are documented and are even
> > suggested in the Microsoft documentation. If this memory
> > leak is not a problem in Cygwin, then these functions
> > should be really easy to implement since they would just
> > call the Win32 APIs.
>
> They are suggested to work around MS's inability to write high-quality
code.
> The calls would be easy to implement yes, but there is no point in putting
> them in *cygwin*.
>
> Rob
>
I agree with Mo. What is the harm in adding "minor" functions which in the
end will help programmers, port and maintain programs more easily. Is that
not the purpose of Cygwin. Anything that reduces the addition of #ifdef
__CYGWIN__ would be a "smart" move in my humble opinion.
Trevor
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2001-07-21 20:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-17 12:59 Mo DeJong
2001-07-17 13:02 ` Christopher Faylor
2001-07-17 14:12 ` Mumit Khan
2001-07-17 15:04 ` Corinna Vinschen
2001-07-17 16:01 ` Mo DeJong
2001-07-18 1:46 ` Corinna Vinschen
2001-07-19 16:13 ` Mo DeJong
2001-07-20 10:09 ` Mumit Khan
2001-07-21 14:26 ` Mo DeJong
2001-07-21 15:02 ` Spaces in User Name Dave BT
2001-07-21 17:07 ` Linking to cygwin1.dll and msvcrt.dll ? Robert Collins
2001-07-21 20:31 ` Trevor Forbes [this message]
2001-07-21 21:24 ` Christopher Faylor
2001-07-22 5:45 ` Robert Collins
2001-07-17 13:36 Steve Jorgensen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='118b01c1125e$e4739390$0300a8c0@ufo' \
--to=trevorforbes@ozemail.com.au \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).