delorie.com/archives/browse.cgi | search |
Date: | Sat, 23 Jun 2001 10:02:05 -0400 |
Message-Id: | <200106231402.KAA29549@envy.delorie.com> |
X-Authentication-Warning: | envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f |
From: | DJ Delorie <dj AT delorie DOT com> |
To: | djgpp-workers AT delorie DOT com |
In-reply-to: | <9743-Sat23Jun2001112024+0300-eliz@is.elta.co.il> |
Subject: | Re: gcc 3.0 released |
References: | <993214856 DOT 8796 DOT 0 DOT camel AT bender DOT falconsoft DOT be> (message from Tim Van Holder on 22 Jun 2001 15:00:55 +0200) <3B339CB9 DOT 13700 DOT D9FD74 AT localhost> <9743-Sat23Jun2001112024+0300-eliz AT is DOT elta DOT co DOT il> |
Reply-To: | djgpp-workers AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | djgpp-workers AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
> If we think GCC 3.0 will be short-lived, and if we have a reason to > believe this particular problem will go away in the next minor > release, perhaps we shouldn't provide 3.0 at all. There is a certain prestige in releasing 3.0 for djgpp as soon as possible, perhaps before other platforms. If 3.0.1 will be out soon, that give us the opportunity to release a 3.0 with less testing, knowing that we can fix whatever needs fixing with 3.0.1.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |