Path: chuka.playstation.co.uk!news
From: gil@snsys.com (Gil Jaysmith)
Newsgroups: scee.yaroze.programming.gnu_compiler
Subject: Re: GNU error refrence?
Date: Mon, 19 Jan 1998 11:53:47 GMT
Organization: PlayStation Net Yaroze (SCEE)
Lines: 48
Message-ID: <34c33aa7.2260291@www-s.playstation.co.uk>
References: <695apk$2ok1@emeka.playstation.co.uk> <34b64c01.2914832@www-s.playstation.co.uk> <34b64db8.3353189@www-s.playstation.co.uk> <34C06219.BEBBC2E4@virgin.net>
NNTP-Posting-Host: trish.snsys.com
X-Newsreader: Forte Free Agent 1.11/32.235

On Sat, 17 Jan 1998 07:47:37 +0000, Ian Thompson
<ian.thomson6@virgin.net> wrote:
>I personally think that Sony should finish off their own GNU
>documentation with an Error/Warning reference. The package, as it stands
>now, is simply incomplete. After all, how many compilers do you know
>that are distributed with system that do not have a proper error
>reference? I suppose it all gets down to whether you believe an error
>reference is optional or an essential. I personally need one.

Unfortunately, you'd better get used to disappointment now you've
joined the console programming arena...

>I  have tried to locate the document at the Free Software Foundation
>home page, I even used DJGPP Zip picker but I could not find it.

That'll be because there isn't one. GCC's errors aren't centralised
like Visual C's. The problem with having so many core coders is that
each has his own error routine. I cite as examples, from different .c
files in the GCC distribution:

- abort()
- exit()
- error()
- my_friendly_abort()
- my_friendly_assert()
- fprintf(stderr, ...)
- warning()
- cp_warning_at()
- warning_with_decl()
- error_with_aggr_type()
- compiler_error()
- sorry()
- fatal_insn_not_found()
- fatal_insn()
- fatal_io_error()
- pfatal_with_name()
...

Some of these functions are called with an error code as well as the
message text, and some aren't. All of them code the message text in
the function call rather than pulling it out of a resource file or
suchlike. Amongst other reasons, this is why you don't see too many
language-localised versions of GCC.

Sorry to be the beaver of bad news, as someone renamed me yesterday,
but there you go.

- Gil