<HTML>
<HEAD>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<TITLE>
    CWG Issue 284</TITLE>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<STYLE TYPE="text/css">
  INS { text-decoration:none; font-weight:bold; background-color:#A0FFA0 }
  .INS { text-decoration:none; background-color:#D0FFD0 }
  DEL { text-decoration:line-through; background-color:#FFA0A0 }
  .DEL { text-decoration:line-through; background-color: #FFD0D0 }
  @media (prefers-color-scheme: dark) {
    HTML { background-color:#202020; color:#f0f0f0; }
    A { color:#5bc0ff; }
    A:visited { color:#c6a8ff; }
    A:hover, a:focus { color:#afd7ff; }
    INS { background-color:#033a16; color:#aff5b4; }
    .INS { background-color: #033a16; }
    DEL { background-color:#67060c; color:#ffdcd7; }
    .DEL { background-color:#67060c; }
  }
  SPAN.cmnt { font-family:Times; font-style:italic }
</STYLE>
</HEAD>
<BODY>
<P><EM>This is an unofficial snapshot of the ISO/IEC JTC1 SC22 WG21
  Core Issues List revision 118b.
  See http://www.open-std.org/jtc1/sc22/wg21/ for the official
  list.</EM></P>
<P>2025-09-28</P>
<HR>
<A NAME="284"></A><H4>284.
  
<I>qualified-id</I>s in class declarations
</H4>
<B>Section: </B>Clause 11&#160; [<A href="https://wg21.link/class">class</A>]
 &#160;&#160;&#160;

 <B>Status: </B>CD1
 &#160;&#160;&#160;

 <B>Submitter: </B>Mike Miller
 &#160;&#160;&#160;

 <B>Date: </B>01 May 2001<BR>


<P>[Moved to DR at October 2002 meeting.]</P>

<P>Although 9.3.4 [<A href="https://wg21.link/dcl.meaning">dcl.meaning</A>] requires that a declaration of
a <I>qualified-id</I> refer to a member of the specified namespace or
class and that the member not have been introduced by a
<I>using-declaration</I>, it applies only to names declared in a
declarator.  It is not clear whether there is existing wording
enforcing the same restriction for <I>qualified-id</I>s in
<I>class-specifier</I>s and <I>elaborated-type-specifier</I>s or
whether additional wording is required.  Once such wording is
found/created, the proposed resolution of
<A HREF="275.html">issue 275</A> must be modified accordingly.</P>

<P><B>Notes from 10/01 meeting:</B></P>

<P>The sentiment was that this should be required on class definitions, but
not on elaborated type specifiers in general (which are references, not
declarations).  We should also make sure we consider explicit instantiations,
explicit specializations, and friend declarations.</P>


<P><B>Proposed resolution (10/01):</B></P>

<P>Add after the end of 11.3 [<A href="https://wg21.link/class.name#3">class.name</A>] paragraph 3:</P>
<BLOCKQUOTE>
When a <I>nested-name-specifier</I> is specified in a
<I>class-head</I> or in an
<I>elaborated-type-specifier</I>, the resulting qualified name
shall refer to a previously declared member of the class or namespace to
which the <I>nested-name-specifier</I> refers, and
the member shall not have been introduced by a
using-declaration in the scope of the class or namespace
nominated by the <I>nested-name-specifier</I>.
</BLOCKQUOTE>

<BR><BR>
</BODY>
</HTML>
