Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!elroy.jpl.nasa.gov!lll-winken!sun-barr!newstop!exodus!exodus-bb!khb From: khb@chiba.Eng.Sun.COM (Keith Bierman fpgroup) Newsgroups: comp.lang.fortran Subject: Re: Compilation listing from Sun F77 Message-ID: Date: 11 Jun 91 05:00:38 GMT References: <1991Jun10.234931.5147@ariel.unm.edu> Sender: news@exodus.Eng.Sun.COM Organization: Sun MegaSystems Lines: 29 In-reply-to: john@spectre.unm.edu's message of 10 Jun 91 23:49:31 GMT In article <1991Jun10.234931.5147@ariel.unm.edu> john@spectre.unm.edu (John Prentice) writes: Why is this? The UNIX Fortran compilers are the only ones I have The cannonical Unix FORTRAN compiler, sif's f77 didn't include one. In many ways, the Unix mindset was defined by the original C compiler and affliated tools. One can argue (as other systems implemented) that compilers should do all sorts of static correctness analysis, cross reference generation and other goodies. However, the Unix tradition/mindset is one task==one tool. miss then. Certainly dbx and dbxtool don't make up for them (and sourcebrowser is a very different tool than dbx. an operating system for people who grove on lots of little utilities). Yes. It's proponents count that as a feature (combined with the usual arguments about the joys of shells, piping, and empowering programmers to build what they want). I don't happen to subscribe to such ideals, for whatever that's worth. -- ---------------------------------------------------------------- Keith H. Bierman keith.bierman@Sun.COM| khb@chiba.Eng.Sun.COM SMI 2550 Garcia 12-33 | (415 336 2648) Mountain View, CA 94043