Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!usc!ucsd!ames!dftsrv!jagubox.gsfc.nasa.gov!jim From: jim@jagubox.gsfc.nasa.gov (Jim Jagielski) Newsgroups: comp.unix.aux Subject: More about FORTRAN compilers Message-ID: <3797@dftsrv.gsfc.nasa.gov> Date: 2 Nov 90 16:45:58 GMT Sender: news@dftsrv.gsfc.nasa.gov Reply-To: jim@jagubox.gsfc.nasa.gov (Jim Jagielski) Distribution: na Organization: NASA/Goddard Space Flight Center Lines: 27 Well, here's just a little bit more to chew on about the NKR vs. Absoft FORTRAN compiler issue that I've been droning on about. I made suggestions to Absoft as well as some asking them some questions (e.g. "Should it REALLY take over 2 1/2 minutes to compile a 1730 line FORTRAN program which is about 1/4 comments?"; "Why did you use non-'standard' ACTION=PRINT instead of CARRIAGECONTROL=FORTRAN?"; "When reopening a pre- connected unit, that unit should NOT be disconnected 1st (in most cases)."; etc...). I have received no answer at all from them... none. Meanwhile I faxed NKR Research and said "You know, it would be a good idea to add COSD, SIND, TAND (etc...) to your FORTRAN library for VAX library compatibility." 2 hours later I got a faxed reply that said "Sounds good... we'll add it to the latest version (which will be shipped out soon)." It don't get much better than that. -- ======================================================================= #include =:^) Jim Jagielski NASA/GSFC, Code 711.1 jim@jagubox.gsfc.nasa.gov Greenbelt, MD 20771 "Kilimanjaro is a pretty tricky climb. Most of it's up, until you reach the very, very top, and then it tends to slope away rather sharply."