This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: A better (more portable) way of printing variable argument lists
- To: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- Subject: Re: A better (more portable) way of printing variable argument lists
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Thu, 26 Feb 1998 17:36:51 -0700
- cc: egcs at cygnus dot com
- Reply-To: law at cygnus dot com
In message <199802261904.OAA08193@caip.rutgers.edu>you write:
> > From: Jeffrey A Law <law@hurl.cygnus.com>
> >
> > Actually, if we're going to revamp how we handle error messages I'd
> > like to see us move more towards a model where we can print errors
> > in multiple languages.
> >
> > Most modern vendor compilers already do this; GCC never tried because
> > RMS opposed numbering warnings/errors (which is how multi-language
> > errors work).
>
> Wouldn't we use gettext? I thought that package used the actual
> message text as the key and that it didn't number messages.
That would be fine too. I'm not particularly wed to the idea of error #s,
they just seem to be the easiest way to index into the message catalog.
If better ways exist, then I see no reason not to use them when the
time comes.
jeff