home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.arch
- Path: sparky!uunet!gatech!rpi!usc!sol.ctr.columbia.edu!The-Star.honeywell.com!umn.edu!kksys.com!edgar!technix!bret
- From: bret@technix.mn.org (Bret Indrelee)
- Subject: Re: 32 => 64 Transition
- Message-ID: <1992Aug23.162814.15668@technix.mn.org>
- Organization: Private System - Saint Paul, MN
- References: <1992Aug18.094549.25179@awdprime.austin.ibm.com> <l9b1usINN2aj@exodus.Eng.Sun.COM> <mcdonald.235@aries.scs.uiuc.edu>
- Date: Sun, 23 Aug 1992 16:28:14 GMT
- Lines: 32
-
- In article <mcdonald.235@aries.scs.uiuc.edu> mcdonald@aries.scs.uiuc.edu (J. D. McDonald) writes:
- >In article <l9b1usINN2aj@exodus.Eng.Sun.COM> chased@rbbb.Eng.Sun.COM (David Chase) writes:
- >
- >> sizeof(INTEGER) = sizeof(REAL) = sizeof(DOUBLE PRECISION)/2.
- >
- >
- >And indeed this is still very much true in Fortran 90.
- >
- >>A corollary of this is that there had better be a 32-bit integer data
- >>type in C, unless your hardware implements quad-word floating point.
- >
- >Don't you mean the your machine needs it for **Fortran**?? That of course
- >essentially decies the issue, as Fortran is still very much alive ...
- >especially for high-end machines. Fortran 90 is probably more or less dead,
- >but not Fortran 77, which remains a standard. That latter is very
- >important .... Fortran 90 is such a botch that to get it passed Fortran
- >77 had to remain an official standard.
-
- The initial statement (there had better be 32-bit integer in C) is correct.
- Some people like to mix languages, calling a C routine from Fortran. I
- suppose the opposite is occasionally done as well, but from what I've seen
- the common case is Fortran calls C.
-
- No language is perfect. It is a good idea to allow mixed language development
- without unneccessary hassles.
-
- -Bret
-
- --
- ------------------------------------------------------------------------------
- Bret Indrelee | Pretend there is something profound
- email: bret@technix.mn.org | written here.
-