home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!sun-barr!cs.utexas.edu!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!uwm.edu!linac!att!ucbvax!efftoo.boeing.com!crispen
- From: crispen@efftoo.boeing.com (crispen)
- Newsgroups: comp.lang.ada
- Subject: Incorporation of Fortran CSCI into Ada system
- Message-ID: <9211091808.AA15494@efftoo.boeing.com>
- Date: 9 Nov 92 18:08:06 GMT
- Sender: daemon@ucbvax.BERKELEY.EDU
- Distribution: world
- Organization: The Internet
- Lines: 23
-
- Russ Johnson asks if anyone has incorporated a Fortran CSCI into
- an existing Ada system. A better question might be whether anyone
- on this list *hasn't* done this ;-)
-
- We've done it just about every way, and the original conclusions
- we came to in the ASVP final report still hold for us: don't recode;
- redevelop. If you have to use the original Fortran, try to make
- sure you've got a real CSCI. The biggest problem with incorporating
- Fortran into Ada is that (because Fortran historically had a high
- penalty on arguments in subroutine calls) people used COMMONs and
- thus lost control over dataflow. Also, particularly with cyclic
- executive architectures, you often didn't care that your first
- few iterations were computing on garbage; Ada obviously does care.
-
- I can't describe the incorporation of Fortran elements as anything
- but "quick and dirty", and I can't describe translation of Fortran
- into Ada-tran as anything but "quick and buggy". Your mileage may
- vary, of course.
- +-------------------------------+--------------------------------------+
- | Bob Crispen | The owls are not what they seem |
- | crispen@foxy.boeing.com +--------------------------------------+
- | (205) 461-3296 |Opinions expressed here are mine alone|
- +-------------------------------+--------------------------------------+
-