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: std::ctype<char>::is doesn't call do_is as required   by ISO 14882
Date: Sun, 14 Oct 2001 13:16:00 -0000	[thread overview]
Message-ID: <20011014201602.2624.qmail@sourceware.cygnus.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1357 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
Subject: Re: libstdc++/4458: std::ctype<char>::is doesn't call do_is as required   by ISO 14882
Date: 14 Oct 2001 22:16:52 +0200

 Martin Sebor <sebor@roguewave.com> writes:
 
 |>  kanze@gabi-soft.de wrote:
 
 |>  > >Number:         4458
 |>  > >Category:       libstdc++
 |>  > >Synopsis:       std::ctype<char>::is doesn't call do_is as required by ISO 14882
 
 |>  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.
 
 -- 
 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


             reply	other threads:[~2001-10-14 13:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-14 13:16 James Kanze [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-21 20:11 rodrigc
2001-12-13  3:36 bkoz
2001-12-13  3:24 bkoz
2001-10-03 10:56 Martin Sebor
2001-10-03 10:26 kanze

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=20011014201602.2624.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: link
Be 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).