Re: Dangerous glibc byte/wide stream interactions

[Harald Alvestrand <Harald at Alvestrand dot no>]

At 10:49 22/09/2000 -0700, Ulrich Drepper wrote:
>Thanks, Bruno.  Exacty correct.  Mixing wide and byte oriented
>functions will (normally) not be checked for since this is just
>punishing correct programs.  The errors are obvious enough to notice.

the behaviour of a (badly behaved) library calling fprintf() on stderr when 
an unexpected error happens and the calling program has already used 
fwritnf() is not going to be obvious enough to notice.

a check (if mode != rightmode {die with snide comment}) would seem 
appropriate, have moderate execution time impact, and would possibly reduce 
the amount of hair loss in C programmers.

                  Harald


-------------------------------------------------
Use Linux? Get counted!
http://counter.li.org - 150.000 and still counting.