From: "Dave Korn" <dave.korn@artimi.com>
To: "'oh no an on-topic post! boooooo!'" <cygwin-talk@cygwin.com>
Subject: RE: life expectancy of gcc 3.x
Date: Wed, 02 Aug 2006 14:24:00 -0000 [thread overview]
Message-ID: <050901c6b63f$54fd7750$a501a8c0@CAM.ARTIMI.COM> (raw)
In-Reply-To: <20060802141508.GA18123@trixie.casa.cgf.cx>
On 02 August 2006 15:15, Christopher Faylor wrote:
> On Wed, Aug 02, 2006 at 09:05:03AM -0500, Charles D. Russell wrote:
>> Would anybody venture an educated guess how much longer gcc 3.x (and
>> hence g77) will be supported by cygwin? gfortran does not seem to offer
>> as many options as g77 for managing archaic code (e.g. from netlib).
>
> Just as a rough seat-of-the pants guesstimate, I'd say that it would be
> supported for at least another 5.99321719 months.
>
> cgf
I'm in no immediate hurry to retire 3.x, as I still don't feel the 4.x
series has stabilised enough to really count as production-ready yet, so you
can reasonably expect 3.x to remain available for a good time yet, and when I
do feel ready to release a 4.x version I'll keep a 3.x version as the 'prev'
version for a fair while after that too.
OTOH a hippo might fall on it at any moment. I can't predict what might
happen then.
cheers,
DaveK
--
Can't think of a witty .sigline today....
next prev parent reply other threads:[~2006-08-02 14:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-02 14:05 Charles D. Russell
2006-08-02 14:15 ` Christopher Faylor
2006-08-02 14:24 ` Dave Korn [this message]
2006-08-02 19:08 ` Igor Peshansky
2006-08-02 19:21 ` Dave Korn
2006-08-02 19:25 ` Igor Peshansky
2006-08-02 19:40 ` mwoehlke
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='050901c6b63f$54fd7750$a501a8c0@CAM.ARTIMI.COM' \
--to=dave.korn@artimi.com \
--cc=cygwin-talk@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).