Path: chuka.playstation.co.uk!news From: gil@snsys.com (Gil Jaysmith (Telecommuting)) Newsgroups: scee.yaroze.programming.gnu_compiler Subject: Re: GNU error refrence? Date: Wed, 28 Jan 1998 22:39:37 GMT Organization: PlayStation Net Yaroze (SCEE) Lines: 29 Message-ID: <34cfb1b9.442177@news.playstation.co.uk> References: <6ahssr$4s31@emeka.playstation.co.uk> <34CE5A1B.1AA33B7E@virgin.net> NNTP-Posting-Host: th-eng03-197.pool.dircon.co.uk X-Newsreader: Forte Free Agent 1.1/32.230 On Tue, 27 Jan 1998 22:05:15 +0000, Ian Thompson wrote: >I allready have GNUINFO.ZIP and unfortunately there isn't an >error/warning refrence within it. You could probably index the actual compiler source with some suitable tool and at least discover which file produced each error message, and where. There's usually something approaching a comment near each error. It's just that there's no centralised error output. It's tempting to do something like that myself as a contribution to the GNU project, but my fear is that such a reference would be (a) inaccurate within one release, (b) not a straightforward project, and (c) a waste of time, since I'd rather such a project came from an urge to localise error messages into one resource, rather than a one-shot dead-ended explanation. The GNU project doesn't accept suggested revisions which are 'just for prettiness' or which require major reimplementation across many files for no functionality increase, or at least that was (FSF inceptor and original GCC lead programmer) Richard Stallman's attitude a while ago. IMHO this sort of attitude is why GCC has the reputation of being incredibly flexible and powerful, but also completely unsupportable and unpredictable. Something will have to be done about GCC (especially C++) at some point - mostly for the pro developers although I expect you'd feel the benefits - but I can't concentrate on it for long enough at the moment :( - Gil