|
From: | Daniel Berlin |
Subject: | Re: Objective-C bugs and GCC releases |
Date: | Tue, 25 Jan 2005 14:02:09 -0500 (EST) |
On Tue, 25 Jan 2005, Adrian Robert wrote:
On Jan 25, 2005, at 9:22 AM, Robert Dewar wrote:Adrian Robert wrote:... Could there be a middle ground to holding up releases for too long waiting for non-market-majority development (a practice which led to the splintering of egcs in the past) on one side and gradually but surely becoming a specialist C/C++ solution on the other?I don't see the point here. Holding up the release does not somehow make more resources available for working on Objective-C. If there are people interested in objective-C, let them work on it. If not, I see no basis for holding up the release.Although it's a volunteer software project, it's also a software project. If broader release criteria are chosen and some of the less popular ones are holding up the release, those who are in a rush to have the release for other features, and have time, might be encouraged to help work on what's holding it up.
So in other words, you want others to do the work for you, by trying to hold *gcc* hostage.
Whether that means actually writing code, or just being a little more tolerant and/or timely in providing advice and guidance to those who _are_ writing the code, it means getting the job done quicker.
People have been very tolerant and timely in providing advice to people attempting to solve objective C issues. As has been pointed out, Richard told Zem how to fix this bug many months ago.
[Prev in Thread] | Current Thread | [Next in Thread] |