public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "eugeny dot klementev at intel dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/13462] New: Non-standard conformed type set::pointer Date: Mon, 22 Dec 2003 11:38:00 -0000 [thread overview] Message-ID: <20031222105150.13462.eugeny.klementev@intel.com> (raw) Your set::pointer defined as: > public: > typedef typename _Rep_type::const_pointer pointer; > typedef typename _Rep_type::const_pointer const_pointer; Where _Rep_type::const_pointer is: > typedef const value_type* const_pointer; But c++ standard 23.3.3 [lib.set] describes set::pointer as non-const pointer: > typedef typename Allocator::pointer pointer; > typedef typename Allocator::const_pointer const_pointer; This inconsistency raise inpossibility of implicit casting "set<char, less<char>, allocator<char> >::pointer" to "allocator<char>::pointer". -- Summary: Non-standard conformed type set::pointer Product: gcc Version: 3.2 Status: UNCONFIRMED Severity: normal Priority: P2 Component: libstdc++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: eugeny dot klementev at intel dot com CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13462
next reply other threads:[~2003-12-22 10:51 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-12-22 11:38 eugeny dot klementev at intel dot com [this message] 2003-12-22 11:39 ` [Bug libstdc++/13462] " eugeny dot klementev at intel dot com 2003-12-22 16:07 ` pinskia at gcc dot gnu dot org 2003-12-22 16:34 ` pinskia at gcc dot gnu dot org 2003-12-22 19:06 ` pinskia at gcc dot gnu dot org 2003-12-22 20:43 ` cvs-commit at gcc dot gnu dot org 2003-12-22 20:45 ` pinskia at gcc dot gnu dot org 2004-01-28 16:34 ` cvs-commit at gcc dot gnu dot org 2004-01-28 16:34 ` pcarlini at suse dot de
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=20031222105150.13462.eugeny.klementev@intel.com \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).