From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <1f1915003de6842de9c38c16c353821a@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] GCC/G++: some stress testing
Date: Sat,  1 Mar 2008 15:29:10 -0500
From: geoff@plan9.bell-labs.com
In-Reply-To: <13426df10803010913w4325a6e9p54a5e4575b6d1754@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 6b5ee24a-ead3-11e9-9d60-3106f5b1d025

Ron, I think you're confusing ratfor with software tools.  There was a
ratfor implementation in C on Unix, and I wrote ratfor when I had to
use Fortran, and others did too, independent of the software tools
effort.  The point of Ratfor was to make Fortran bearable; I can't
imagine writing bare Fortran any more.

I compiled ratfor and f2c on my home Plan 9 systems a while ago and
they just worked.  I don't remember any porting effort.  I might have
had to change a path name in a makefile.