public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "arjun.is at lostca dot se" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug stdio/17522] `fputws' errors out when writing wide characters to unbuffered stream Date: Wed, 29 Oct 2014 19:12:00 -0000 [thread overview] Message-ID: <bug-17522-131-pzlizYigwb@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-17522-131@http.sourceware.org/bugzilla/> 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.
next prev parent reply other threads:[~2014-10-29 19:12 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-10-29 15:57 [Bug stdio/17522] New: " arjun.is at lostca dot se 2014-10-29 18:03 ` [Bug stdio/17522] " carlos at redhat dot com 2014-10-29 18:43 ` arjun.is at lostca dot se 2014-10-29 18:49 ` carlos at redhat dot com 2014-10-29 19:12 ` arjun.is at lostca dot se [this message] 2014-10-29 19:16 ` carlos at redhat dot com 2014-11-03 9:00 ` cvs-commit at gcc dot gnu.org 2014-11-03 9:03 ` schwab@linux-m68k.org 2014-12-16 11:26 ` cvs-commit at gcc dot gnu.org 2023-12-20 15:43 ` fweimer at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-17522-131-pzlizYigwb@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).