[LLVMbugs] [Bug 20250] New: No diagnostic where using-declaration names entity not found by class member name lookup in any direct base
bugzilla-daemon at llvm.org
bugzilla-daemon at llvm.org
Tue Jul 8 14:22:48 PDT 2014
http://llvm.org/bugs/show_bug.cgi?id=20250
Bug ID: 20250
Summary: No diagnostic where using-declaration names entity not
found by class member name lookup in any direct base
Product: clang
Version: trunk
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P
Component: C++
Assignee: unassignedclangbugs at nondot.org
Reporter: hstong at ca.ibm.com
CC: dgregor at apple.com, llvmbugs at cs.uiuc.edu
Classification: Unclassified
In N3937 subclause 7.3.3 [namespace.udecl] paragraph 17:
The base class members mentioned by a using-declaration shall be visible in the
scope of at least one of the direct base classes of the class where the
using-declaration is specified.
The same is present in C++03 (under paragraph 14).
This wording is perhaps an abuse of the term "scope"; however, I believe that
the using-declaration for B::Foo in D is intended to be invalid in the case
below.
EDG produces the following message:
"udecl.cc", line 5: error: class member designated by a using-declaration must
be visible in a direct base class
using B::Foo;
^
### SOURCE:
> cat udecl.cc
struct B { struct Foo; };
struct C : B { void Foo(); };
struct D : C {
using B::Foo;
typedef Foo Bar;
};
Return: 0x00:0
### COMPILER INVOCATION AND OUTPUT:
> clang++ udecl.cc -std=c++03 -Wall -Wextra -pedantic-errors -c
Return: 0x00:0
### EXPECTED OUTPUT:
A diagnostic.
### COMPILER VERSION INFO:
> clang++ -v
clang version 3.5.0
Target: powerpc64-unknown-linux-gnu
Thread model: posix
Found candidate GCC installation: /usr/lib/gcc/ppc64-redhat-linux/4.4.4
Found candidate GCC installation: /usr/lib/gcc/ppc64-redhat-linux/4.4.6
Selected GCC installation: /usr/lib/gcc/ppc64-redhat-linux/4.4.6
Candidate multilib: .;@m64
Candidate multilib: 32;@m32
Selected multilib: .;@m64
Return: 0x00:0
--
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20140708/ab4a4b11/attachment.html>
More information about the llvm-bugs
mailing list