public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: dv@vollmann.ch To: gcc-gnats@gcc.gnu.org Cc: dv@vollmann.ch Subject: c++/10473: conversion operator from private base used Date: Wed, 23 Apr 2003 23:56:00 -0000 [thread overview] Message-ID: <200304232344.BAA29081@vollmann.ch> (raw) >Number: 10473 >Category: c++ >Synopsis: g++ wrongly considers conversion operator from private base >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: rejects-legal >Submitter-Id: net >Arrival-Date: Wed Apr 23 23:56:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Detlef Vollmann >Release: 3.4 20030423 (experimental) >Organization: vollmann engineering gmbh >Environment: System: Linux dwarf 2.4.3-XFS #7 Mon Aug 6 18:43:20 CEST 2001 i686 unknown Architecture: i686 host: i686-pc-linux-gnu build: i686-pc-linux-gnu target: i686-pc-linux-gnu configured with: /pdsrc/gcc/cvs/gcc/configure --program-suffix=-test --prefix=/local/gcc-test --enable-shared --enable-threads=posix --enable-version-specific-runtime-libs --enable-languages=c,c++ >Description: If a class defines an operator[] and a private base class defines a conversion operator to a pointer, the use of the operator[] can cause ambiguities. This would be correct if the derivation would be public, but is wrong if the derivation is private. >How-To-Repeat: See attached file: inherit-conv.cc: typedef unsigned int size_t; class Base { public: typedef int *value_type; Base() {} operator value_type() const { return 0; } void operator=(value_type val) {} }; class Derived : private Base { public: Derived() : p(0) {} Base::value_type &operator[](size_t index) { return p; } private: Base::value_type p; }; int main() { Derived ppBuf; int *p = ppBuf[4]; ppBuf[0] = p; return 0; } >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2003-04-23 23:56 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200304232344.BAA29081@vollmann.ch \ --to=dv@vollmann.ch \ --cc=gcc-gnats@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).