Path: utzoo!attcan!uunet!samsung!zaphod.mps.ohio-state.edu!usc!snorkelwacker!ira.uka.de!smurf!ipkama!ferstl From: ferstl@ipkima.uucp (Fritz Ferstl) Newsgroups: comp.lang.fortran Subject: > Wanted: DOS Fortran Compiler for 386 instruction set. Message-ID: <90.256.12:32:25@ipkima.uucp> Date: 13 Sep 90 10:32:25 GMT Distribution: comp Organization: Integrated Parallel Systems KG Woest ; Kiel , FRG Lines: 36 In comp.lang.fortran you write: >Need information re: DOS Fortran Compiler for 386 instruction set. >Any information on availabilty/ references/ recommendations appreciated. >Ben olasov@cs.columbia.edu The most advanced DOS FTN-Compiler for 386 IS I know from is the new Lahey Compiler (I don't rember the type secification an the version, but Lahey is well known, so you should get it). I read about it in the German magazine C't. There was a comparison between the Lahey and others which support some kind of memory extensions. The Lahey was one of the few (and the best of all) that also supports the 386 IS. The author claimed: The Lahey Compiler is very fast, both according the compile time (some 1000 lines source codes in some seconds - high optimization). In order to use memory extensions you have to compile especially for this purpose and execute your programs via `run prog' or something like that. The main dis- advantages seemed to be development environment (nothing integrated like Borland or newer MicroSoft compilers with editor, debugger and so on) and price (s.th. around or above 1000 $). Unfortunately I haven't used this compiler (im working with UNIX, thereforeI'm looking for a good FTN Compiler too). So I can't tell you about personal experiences. Nevertheless, I hope s.th. of the above is true :-( Fritz ========================================================================== Fritz Ferstl, iP-Systems, Steinhaeuserstr. 20, 7500 Karlsruhe 1, W-Germany Phone: +49 + 721 + 811091 (VOICE) - 811095 (FAX) - 811096 (PEP) E-Mail: ferstl@ipkama.ka.sub.org ==========================================================================