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 proceed with the numbering.
That is the plan, only there is allot of work.. i should come up with
something to automate it.
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: aaaa-bbbbbb: where aaaa is
assigned to a particular program and bbbbbbb is the unique number
within the program (as you described). Perhaps the aaaa part is what
you intended for the 'c' in your example below. I would make it more
explicit. e.g. gcc1001 at least.
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?
I'm not clear on your question. If you are asking how is the aaaa
part assigned to a particular program, I don't know the details but
there was someone who controlled the list of numbers already given out.
I don't know how GNU does internationalization. But in AIX-land,
this is the first step. The messages are in the code and also in a
message file. If no language is specified in the user's environment,
the message in the code is used. If a language is specified (I'm
talking about the user's spoken language), then the message is looked
up in a file based upon the LANG and NLS environment variables.
My warning is that this triggers a somewhat substantial support
effort. As new messages are added, their translations should be
created and added to each language file.
Sorry i don't see how language support has to do anything with this.
Could you explain?
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).
With all that aside, as a user of gcc, I think it is a great idea --
especially if it crept over into all of GNU's products.
Great to hear that! I'm planning to set up a website(wiki?) so more
people can actually work on it. Making patches (or a auto-patching
script) is the plan so you can get the gcc-core and run the tool on
it. Other programming languages can follow up if this works out and if
there is actually interest for it.
