home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.sgi
- Path: sparky!uunet!sun-barr!ames!sgi!quasar.wpd.sgi.com!davea
- From: davea@quasar.wpd.sgi.com (David B.Anderson)
- Subject: Re: cc errors
- Message-ID: <nqvu64k@sgi.sgi.com>
- Sender: davea@quasar.wpd.sgi.com
- Organization: Silicon Graphics, Inc. Mountain View, CA
- Date: Mon, 27 Jul 1992 17:57:31 GMT
- Lines: 30
-
- In article <1992Jul27.103035.26247@bernina.ethz.ch> hoesel@igc.ethz.ch (Frans van Hoesel) writes:
- >I don't like the lengthy error messages from the c-compiler.
- >They fill the screen
- >with lots of dashes even if one makes only a few mistakes.
- >This behavior is *NOT* what is described in the ansi-c manual from sgi.
- >there is some page describing exactly what the format of the
- >error messages is. The format described there is not the format I get.
- >Any way to force this output format?
- >(this is still 4.0.1)
- >
- >-- frans
-
- Sorry you don't like the messages. While I do :-), it clearly would be
- desirable to give users control over verbosity. Can't promise when
- that will happen. I believe it will happen, though.
-
- The dashes attempt to show exactly where the compiler thinks the error is.
- If there are lots of dashes then you have very long source lines (after
- preprocessing). On really long lines the dashes are sometimes not
- helpful. Tough for the compiler to know which are useful.
-
- The present output of *multiple* messages on a single error inflates the
- output a lot. This was never *desirable*, but did make compiler maintenance
- easier (for reasons I won't go into).
-
- Thanks for the input.
-
- Regards,
- [ David B. Anderson (415)390-1548 davea@sgi.com ]
-
-