J_SCHULL%HVRFORD.BITNET@cornellc.cit.cornell.edu (Jonathan Schull) (02/09/90)
I've got some Fortan77 code that I want to splice into a Turbo 5 program. Or should I work on interfacing object codes, etc? If the latter, what does that entail ?!
reeves@dvinci.usask.ca (Malcolm Reeves) (02/16/90)
From article <22404@adm.BRL.MIL>, by J_SCHULL%HVRFORD.BITNET@cornellc.cit.cornell.edu (Jonathan Schull): I've had the same problem. My solution is: Strip all the I/O out of the FORTRAN - this usually reduces the size of .exe files considerably. Exec the compiled FORTRAN from TP5 - make sure you use IEEE number formats in both languages. Pass data by reading external files - I use unformatted FORTRAN records which are easy to read in TP5 - ASCII is much slower. I use this alot for large numerical codes in FORTRAN so that TP5 can provide a more convenient "front end" and more flexible graphics post-processing. It avoids replacing large amounts of relatively efficient bug-free FORTRAN but allows you to use all the good things in TP5. If anyone can tell me how to access "COMMON BLOCKS" after a TP5 exec I could avoid alot of file writing. It should be possible to "find" the memory addresses and hook the data with pointers but life's too short .....