<HTML>
<HEAD>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<TITLE>
    CWG Issue 194</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="194"></A><H4>194.
  
Identifying constructors
</H4>
<B>Section: </B>11.4.5&#160; [<A href="https://wg21.link/class.ctor">class.ctor</A>]
 &#160;&#160;&#160;

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

 <B>Submitter: </B>Jamie Schmeiser
 &#160;&#160;&#160;

 <B>Date: </B>11 Jan 2000<BR>





<P>According to 11.4.5 [<A href="https://wg21.link/class.ctor">class.ctor</A>]
paragraph
1, the syntax used in declaring a constructor allows at most one
<I>function-specifier</I>.  It is thus not permitted to declare a
constructor both <TT>inline</TT> and <TT>explicit</TT>.  This seems
overly restrictive.</P>

<P>On a related note, there doesn't seem to be any explicit
prohibition against member functions with the same name as the class.
(Such a prohibition might reasonably be expected to occur in
11.4 [<A href="https://wg21.link/class.mem#13">class.mem</A>] paragraph 13,
 but member
functions are not listed there.)</P>

<P>One possible interpretation would be that such member functions
would violate the restrictions in
6.4.7 [<A href="https://wg21.link/basic.scope.class#1">basic.scope.class</A>] paragraph 1,

because the class name would refer to the class at some points in the
class scope and to the member function at others.  However, this seems
a bit tenuous.  Is an explicit prohibition needed?</P>

<P>(See also <A HREF="147.html">issue 147</A>.)</P>

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

<OL>
<LI>
<P>Add to 11.4 [<A href="https://wg21.link/class.mem#13">class.mem</A>] paragraph 13</P>

<BLOCKQUOTE>
<UL><LI>every member function of class <TT>T</TT> [<I>Note:</I> this
restriction does not apply to constructors, which do not have names
(11.4.5 [<A href="https://wg21.link/class.ctor">class.ctor</A>]). ];</LI></UL>
</BLOCKQUOTE>

<P>immediately following the line</P>

<BLOCKQUOTE>
<UL><LI>every data member of class <TT>T</TT>;</LI></UL>
</BLOCKQUOTE>
</LI>

<LI>
<P>Change 11.4.5 [<A href="https://wg21.link/class.ctor#1">class.ctor</A>] paragraph 1 from</P>

<BLOCKQUOTE>
A special declarator syntax using an optional
<I>function-specifier</I> (9.2.3 [<A href="https://wg21.link/dcl.fct.spec">dcl.fct.spec</A>])...
</BLOCKQUOTE>

<P>to</P>

<BLOCKQUOTE>
A special declarator syntax using an optional sequence of
<I>function-specifier</I>s (9.2.3 [<A href="https://wg21.link/dcl.fct.spec">dcl.fct.spec</A>])...
</BLOCKQUOTE>
</LI>
</OL>
<BR><BR>
</BODY>
</HTML>
