public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Paolo Carlini <pcarlini@unitus.it> To: paolo@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: libstdc++/9024: Input fails after call to basic_filebuf<>::pubsetbuf(0, 0) Date: Mon, 03 Mar 2003 10:56:00 -0000 [thread overview] Message-ID: <20030303105601.2463.qmail@sources.redhat.com> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1213 bytes --] The following reply was made to PR libstdc++/9024; it has been noted by GNATS. From: Paolo Carlini <pcarlini@unitus.it> To: =?ISO-8859-1?Q?P=E9tur_Run=F3lfsson?= <peturr02@ru.is> Cc: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, paolo@gcc.gnu.org, gcc-prs@gcc.gnu.org, bkoz <bkoz@redhat.com> Subject: Re: libstdc++/9024: Input fails after call to basic_filebuf<>::pubsetbuf(0, 0) Date: Mon, 03 Mar 2003 11:45:47 +0100 Pétur Runólfsson wrote: >>A memo: while working on a fix for libstdc++/9423 (quite easy >>by itself), >>finally seems obvious how to fix 9024: in _M_underflow_common add a >>separate case for !__testget && !__testinit, which simply calls >>_M_file.xsgetn(&__c, 1) and returns __ret = >>traits_type::to_int_type(__c). >> >> >Does this work when codecvt::encoding() != 1 ? > One thing at a time Pétur! Your problem report was about plain chars, right? Eventually, _M_underflow_common(wchar_t) will obviously include something along these lines (the approach works, by the way), taking into account encoding() to fetch the appropriate number of external bytes decoded to get one internal char, together with other fixes for 9178 and 9875. Paolo.
next reply other threads:[~2003-03-03 10:56 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-03 10:56 Paolo Carlini [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-03 10:46 Pétur Runólfsson 2003-03-02 21:26 Paolo Carlini 2002-12-20 14:34 paolo 2002-12-20 11:26 Paolo Carlini 2002-12-20 11:16 paolo 2002-12-20 11:07 paolo 2002-12-20 6:46 peturr02
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=20030303105601.2463.qmail@sources.redhat.com \ --to=pcarlini@unitus.it \ --cc=gcc-prs@gcc.gnu.org \ --cc=paolo@gcc.gnu.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).