public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Martin Sebor <sebor@roguewave.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: libstdc++/4458 Date: Sun, 14 Oct 2001 14:06:00 -0000 [thread overview] Message-ID: <20011014210601.15418.qmail@sourceware.cygnus.com> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1289 bytes --] The following reply was made to PR libstdc++/4458; it has been noted by GNATS. From: Martin Sebor <sebor@roguewave.com> To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, kanze@gabi-soft.de, gcc-bugs@gcc.gnu.org Cc: Subject: Re: libstdc++/4458 Date: Sun, 14 Oct 2001 15:02:40 -0600 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. Regards Martin
next reply other threads:[~2001-10-14 14:06 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-10-14 14:06 Martin Sebor [this message] 2001-10-28 2:16 libstdc++/4458 James Kanze 2001-10-29 8:36 libstdc++/4458 Phil Edwards
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=20011014210601.15418.qmail@sourceware.cygnus.com \ --to=sebor@roguewave.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).