public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "David Abrahams" <david.abrahams@rcn.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: libstdc++/3759: nonconforming use of unqualified std:: names Date: Thu, 26 Jul 2001 05:46:00 -0000 [thread overview] Message-ID: <20010726124604.20942.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR libstdc++/3759; it has been noted by GNATS. From: "David Abrahams" <david.abrahams@rcn.com> To: "Gabriel Dos Reis" <gdr@codesourcery.com> Cc: <rittle@labs.mot.com>, "Gabriel Dos Reis" <gdr@codesourcery.com>, <gcc-bugs@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org> Subject: Re: libstdc++/3759: nonconforming use of unqualified std:: names Date: Thu, 26 Jul 2001 08:36:13 -0400 ----- Original Message ----- From: "Gabriel Dos Reis" <gdr@codesourcery.com> > "David Abrahams" <david.abrahams@rcn.com> writes: > > The bottom line is that, we have an issue as to know which functions a > library can use unqualified. As to now, there has been no definitive > resolution. Oh yes, one can modify insert() to please you, but that > doesn't answer the question of which function names the libray can use > in an unqualified manner. The answer to that question is necessary > before going changing function name uses willy-nilly. I think we've reached an end of this debate. I understand that we disagree, but I the use of the term "willy-nilly" and the question of pleasing me personally is an unfair characterization. You understand the issue differently from me. I can respect that. I even think you misunderstand the issue, but I don't think you're being irresponsible, as the term "willy-nilly" would imply. Just to reiterate my position: regardless of the question of which names may be used unqualified, the library must meet its specification. The places where the question of the use of unqualified names are relevant are those where the library specification says that a particular function is used in the implementation of another function. Examples are in valarray and swap_ranges. I filed a bug report against libstdc++ concerned with the semantics of insert() and the large majority of other functions which are not documented as calling other standard algorithms precisely because the correctness of their implementation with respect to the standard is easy to determine. I did not touch on the issue of valarray and swap_ranges because the right thing to do, as Gaby implies, is not yet clear. And now, with respect, I withdraw from this discussion. Regards, Dave
next reply other threads:[~2001-07-26 5:46 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-07-26 5:46 David Abrahams [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-07-26 6:36 David Abrahams 2001-07-26 6:26 Gabriel Dos Reis 2001-07-26 6:16 David Abrahams 2001-07-26 5:56 Gabriel Dos Reis 2001-07-25 15:46 Gabriel Dos Reis 2001-07-25 15:36 David Abrahams 2001-07-25 14:56 Gabriel Dos Reis 2001-07-25 14:16 Loren James Rittle 2001-07-24 11:26 Gabriel Dos Reis 2001-07-24 11:06 Gabriel Dos Reis 2001-07-24 10:46 Gabriel Dos Reis 2001-07-24 10:36 David Abrahams 2001-07-24 10:16 Gabriel Dos Reis 2001-07-24 10:06 David Abrahams 2001-07-24 9:36 Gabriel Dos Reis 2001-07-23 16:23 ljrittle 2001-07-21 11:36 david.abrahams
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=20010726124604.20942.qmail@sourceware.cygnus.com \ --to=david.abrahams@rcn.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).