home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.fortran
- Path: sparky!uunet!news.claremont.edu!nntp-server.caltech.edu!draco.macsch.com!convex.is.macsch.com!dnl
- From: dnl@convex.is.macsch.com (David Lombard)
- Subject: Re: Fortran to C issues?
- Message-ID: <1992Nov19.161826.9902@draco.macsch.com>
- Sender: usenet@draco.macsch.com (Usenet Poster)
- Organization: MacNeal-Schwendler Corp.
- References: <BxtKJL.2Ir@accelr8.com> <1992Nov17.224350.26781@draco.macsch.com> <1992Nov18.183132.16770@newshost.lanl.gov>
- Date: Thu, 19 Nov 92 16:18:26 GMT
- Lines: 30
-
- In article <1992Nov18.183132.16770@newshost.lanl.gov> jlg@cochiti.lanl.gov (J. Giles) writes:
- >In article <1992Nov17.224350.26781@draco.macsch.com>, dnl@convex.is.macsch.com (David Lombard) writes:
- >|> [...]
- >|> Finally, and this will change with time, Fortran compiler writers have
- >|> more experience in highly optimized code than do C compiler
- >|> writers. That's a temporary advantage at best.
- >|>
- >|> On C's side, have you ever seen code which dealt with bitmaps, free
- >|> memory chains, complicated structures and the like in Fortran? Talk
- >|> about terminally ugly and begging for coding errors!
- >
- >Yes, but this is a temporary problem - more temporary than the one you
- >excused C for just now. Fortran 90 has support for all this stuff.
- >Most better implementations of Fortran have had *some* support for
- >quite a while, but many vendors were waiting for the standard before
- >committing themselves (an example of "cart before the horse" since
- >the standard should be driven by common practice, not the other way
- >around).
- >
-
- Fair comment!
-
- Regards,
- DNL
-
- MY_COMMENTS = MY_OPINIONS = NOBODY_ELSES;
-
- David N. Lombard The first thing we do, The MacNeal-Schwendler Corp
- dnl@macsch.com Let's kill all the lawyers. 815 Colorado Blvd
- (213) 259-4911 II Henry VI, IV.ii Los Angeles, CA 90041
-