🚀 go-pugleaf

In article <9525008.24470@mulga.cs.mu.OZ.AU>
           fjh@munta.cs.mu.OZ.AU "Fergus Henderson" writes:

> kanze@lts.sel.alcatel.de (James Kanze US/ESC 60/3/141 #40763) writes:
> 
> >matt@godzilla.EECS.Berkeley.EDU (Matt Austern) writes:
> >
> >|> There's nothing wrong with a C++ implementation parsing
> >|> printf's format string at compile time, doing error checking to
> >|> make sure that there aren't any type errors, and putting in the
> >|> appropriate low-level calls.
[snip]
> >
> >Actually, I doubt it.  Normally, the format string in production code
> >will not be a string literal, but rather something read from a
> >configuration file, dependant on the locale setting.
> 
> That has not been my observation.
> 
> >Or do you really think everyone in the world can read English
> >fluently.
> 
> That's not relevant.  The issue is optimization, not
> internationalization.  What is relevant is that in many C programs,

If you worked in Europe then locale settings are relevent and important. 
For example on the Swiss electronic stock exchange project, All screens 
for the dealers have to be presented in German, French and English. 
Without correct implementations of locale, the job of programming 
the screens to be canton configrable would have been much more complicated.

The German: 100,001 is the same as in English 100.001.
To a German "100.001" means one hundered thousand and one".

-- 
Regards Philip Shearer 
 
Civilization advances by extending the number of important operations which we
can perform without thinking of them.