On Sun, 15 Jan 2006 10:40:19 -0600, Perry Smith wrote:
> From Andreas's reply, it may not. In AIX, they want the message to
>come out in the user's native language so they print out the
>translated message (that comes from a separate file).
It's the same with gettext. You have a file contain
[..snip..]
> At some stage it was decided to pad error codes so that they were equal in
> legnth(string wise). I don't know why, but perhaps it can be useful to know.
I think this will introduce problems when more messages are added
overtime or it wont if the length is large enough. Besides that
On Sunday 15 January 2006 10:59, rubicant rubicant wrote:
> I'm trying to suggest that GCC should have error codes to describe
> errors, continue reading on if you like the idea or not ;-)
>
> THE IDEA:
> The idea is to make GCC better when it comes to error reporting. This
> will be done using so
On Jan 15, 2006, at 10:14 AM, rubicant rubicant wrote:
[..snip..]
1) What if the same warning or error message comes from two places?
Your numbering system would make this hard to identify. I would
suggest gathering up all the errors and warnings from all the files,
remove duplicates, then p
rubicant rubicant <[EMAIL PROTECTED]> writes:
[...]
| The `c' was a example for the C programming language, so the
| error/warning message gets into a category rather indicating the
| program and do you have any idea how they do it in AIX?
How is that different from the named-daignostic switch i
[..snip..]
> 1) What if the same warning or error message comes from two places?
> Your numbering system would make this hard to identify. I would
> suggest gathering up all the errors and warnings from all the files,
> remove duplicates, then proceed with the numbering.
That is the plan, only t
Perry Smith <[EMAIL PROTECTED]> writes:
> 2) AIX (yea, I know thats a ick term) attempts to have a consistent
> numbering system across the whole platform. This is done by
> splitting the number into two pieces: -bb: where is
> assigned to a particular program and bbb is th
Two comments:
1) What if the same warning or error message comes from two places?
Your numbering system would make this hard to identify. I would
suggest gathering up all the errors and warnings from all the files,
remove duplicates, then proceed with the numbering. Or... it may be
tha
I'm trying to suggest that GCC should have error codes to describe
errors, continue reading on if you like the idea or not ;-)
THE IDEA:
The idea is to make GCC better when it comes to error reporting. This
will be done using so called error codes which then can be looked up
in a properly
formatte
