public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: James Kanze <kanze@YAST_ASK.sourceware.cygnus.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: libstdc++/4458 Date: Sun, 28 Oct 2001 02:16:00 -0000 [thread overview] Message-ID: <20011028101600.20949.qmail@sourceware.cygnus.com> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 2181 bytes --] The following reply was made to PR libstdc++/4458; it has been noted by GNATS. From: James Kanze <kanze@YAST_ASK> To: Martin Sebor <sebor@roguewave.com> Cc: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org Subject: Re: libstdc++/4458 Date: 28 Oct 2001 12:16:01 +0100 Martin Sebor <sebor@roguewave.com> writes: |> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=4458&database=gcc |> |> It's not required to do so for efficiency (see 22.2.1.3.2, p5). |> §22.2.1.1.1/1: concerning std::ctype<>::is: |> Returns: do_is(m,c) |> Can't be any clearer than that. The function do_is is required by |> the standard to be virtual, which means that the actual function |> called (and thus the actual semantics of the function is) depend on |> the dynamic type of the object. This is, after all, the whole |> point behind defining the protected virtual functions -- any other |> interpretation, and having the protected interface makes sense. |> No, you're quoting the requirement on the primary template, but your |> issue (titled std::ctype<char>::is ...) is with the specialization |> on char. The requirement I referred you to in 22.2.1.3.2, p5 is the |> one that's relevant here. The reason for not calling the virtual |> function from the ctype<char>::is() is, as I said earlier, for |> efficiency. I've found it now. It never occurred to me that the standard could require that a specialization have different semantics than the basic template. I guess the bug is in the standard, and not in g++. I conclude that if I want to implement the iso_8859_1 locale for ctype, it should be sufficient to provide the correct table. I don't need it for my current work, so finding time for it isn't necessarily easy, but if I can get around to it, do I have to do anything special to get it integrated into the normal g++ releases? -- James Kanze mailto:kanze@gabi-soft.de Conseils en informatique orientée objet/ Beratung in objektorientierter Datenverarbeitung Ziegelhüttenweg 17a, 60598 Frankfurt, Germany Tel. +49(0)179 2607481
next reply other threads:[~2001-10-28 2:16 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-10-28 2:16 James Kanze [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-10-29 8:36 libstdc++/4458 Phil Edwards 2001-10-14 14:06 libstdc++/4458 Martin Sebor
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=20011028101600.20949.qmail@sourceware.cygnus.com \ --to=kanze@yast_ask.sourceware.cygnus.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).