Xref: utzoo alt.sys.sun:2661 comp.lang.fortran:4706 Path: utzoo!utgpu!cs.utexas.edu!uunet!maverick.ksu.ksu.edu!unmvax!ariel.unm.edu!ghostwheel.unm.edu!john From: john@ghostwheel.unm.edu (John Prentice) Newsgroups: alt.sys.sun,comp.lang.fortran Subject: Re: How Broken is Sun Fortran (Summary) Message-ID: <1991Feb08.055745.8468@ariel.unm.edu> Date: 8 Feb 91 05:57:45 GMT References: <1991Feb04.013025.8087@ariel.unm.edu> <1991Feb4.194628.12615@tukki.jyu.fi> <49413@seismo.CSS.GOV> <1991Feb8.023527.20806@fs7.ece.cmu.edu> Organization: University of New Mexico, Albuquerque, NM Lines: 28 In article <1991Feb8.023527.20806@fs7.ece.cmu.edu> winstead@faraday.ECE.CMU.EDU (Charles Holden Winstead) writes: > > 1- Is Fortran on these Suns different than 'conventional' Fortran? i.e. > what do I have to look out for? > We have ported a large number of codes from PC's and Cray's to Sun Fortran. I have not found anything in Sun Fortran that has caused problems. It seems to include everything in the Fortran 77 standard. There are additions as well, specific to Sun. They only one we are making significant use of are the Fortran pointers (which work identically to how Cray uses them, something that came as a pleasant surprise to us). We use they in conjunction with calls to malloc (which Sun Fortran provides a nice Fortran interface to, saving you the trouble) to perform dynamic dimensioning. We use this feature extensively and have never had any problems. In general, I am fairly impressed by Sun Fortran. Our only complaint has been some bugs in 1.3.1 which have caused us problems, particularly of late. However, to be fair, we have used this compiler ALOT and only recently have we run into major problems. I am assured that these problems have been fixed in the new release, so that should not be regarded as a major stumbling block. John -- John K. Prentice john@unmfys.unm.edu (Internet) Dept. of Physics and Astronomy, University of New Mexico, Albuquerque, NM, USA Computational Physics Group, Amparo Corporation, Albuquerque, NM, USA