[Bug stdio/17522] `fputws' errors out when writing wide characters to unbuffered stream

[arjun.is at lostca dot se]

https://sourceware.org/bugzilla/show_bug.cgi?id=17522

--- Comment #5 from Arjun Shankar <arjun.is at lostca dot se> ---
(In reply to Carlos O'Donell from comment #4)
> It's a QoI issue.

Yes.

> For example, printing ASCII, should just print right away, it's unbuffered,
> and that's valid UTF-8. It should not be a naive implementation where you
> might have 4 ASCII characters waiting in a buffer before being printed.

Agreed. I incorrectly used the word 'buffer' in my comment. What I was trying
to say is that ideally, the encoder should have enough "internal memory" to
convert the internal representation of a wide character into the one used by
the current encoding scheme.

Which brings us back to the question of:

* we do this?:
> Thus tst-skeleton.c needs to be enhanced to allow the test to define the
> size of the stdout buffer it needs and then that can be allocated and passed
> to setvbuf

* or this?:
> enhance the file stream support to do this when unbuffered.

-- 
You are receiving this mail because:
You are on the CC list for the bug.