Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-ID: <51896.213.38.17.50.1041875338.squirrel@raq299.uk2net.com>
In-Reply-To: <20030106165836.GE25858@redhat.com>
References: <20030106065320 DOT E6109407C AT sitemail DOT everyone DOT net> 
     <20030106155840 DOT GC25858 AT redhat DOT com> 
     <46935 DOT 213 DOT 38 DOT 17 DOT 50 DOT 1041869937 DOT squirrel AT raq299 DOT uk2net DOT com> 
     <20030106165836 DOT GE25858 AT redhat DOT com>
Date: Mon, 6 Jan 2003 17:48:58 -0000 (GMT)
Subject: Re: Re: help for compiling problem!
From: "Dave Hooper" <dave AT beermex DOT com>
To: cygwin AT cygwin DOT com
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
X-Priority: 3
Importance: Normal

>>As a follow up to this, and the earlier thread regarding icmp (which
>>presumably is resolved in the same way), would it not be "better" to add
>>support for the icmp function and setlinebuf to cygwin?
>
> What are you suggesting?  That there should be an eager team of
> engineers standing by waiting for requests for unimplemented features?
> That sort of pushes all of the responsibility off onto cygwin.
[...snip...]
> Cygwin is different since it is open source and development moves faster
> than something like HP/UX, however, the logic of sending linker errors
> to a mailing list and waiting days for someone to respond, escapes me.

Sorry to have caused confusion.  It wasn't my intention to p.o. any cygwin
developers (you'll note that I was not the author of the original post,
only the author of the subsequent reply).

> When you port software to new systems, you often have to tweak the
> software to accommodate the new system.

I do not dispute that.  However my response was coming from the
perspective of a developer who uses cygwin tools to get things done,
rather than as a *nix developer porting code to run under cygwin, or a
cygwin developer maintaining or extending cygwin.  You weren't necessarily
to know this of course!

> Also, if *you* want functionality, *you* can add it.

That's actually what I had in mind.  I was never going to suggest anyone
else would implement it :-)

> I wouldn't be surprised to see someone offer setlinebuf now.  That's what
> new cygwin releases are for.
[...]
> In this case, I happen to know that working around the problem is
> trivial.  It should be so trivial that a few minutes inspection of a man
> page is all that is required.

Ok, bad example.  I apologise.

> For icmp functionality, we obviously use whatever Windows provides.
> I have no idea if it is possible to implement.

I know that icmp is non-trivial in Windows, but your reply suggests it
isn't provided in cygwin.  I'll look into this.

d

--
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/