From: Brendan Kehoe <brendan@gcc.gnu.org>
Date: Fri, 10 Oct 1997 00:05:55 +0000 (-0400)
Subject: add an initial very rough description of how `explicit' is handled
X-Git-Tag: releases/egcs-1.0.0~358
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=e050253aa5c19dd6ff943cb1e1a660d95c08c18e;p=thirdparty%2Fgcc.git

add an initial very rough description of how `explicit' is handled

From-SVN: r15883
---

diff --git a/gcc/cp/gxxint.texi b/gcc/cp/gxxint.texi
index 5b7f9132aca9..975512ca5570 100644
--- a/gcc/cp/gxxint.texi
+++ b/gcc/cp/gxxint.texi
@@ -238,6 +238,13 @@ The functions @code{convert_to_aggr} and @code{build_method_call} use
 a given candidate function (that's how we get the list of candidates for
 @code{ideal_candidate}).
 
+@item The Explicit Keyword
+
+The use of @code{explicit} on a constructor is used by @code{grokdeclarator}
+to set the field @code{DECL_NONCONVERTING_P}.  That value is used by
+@code{build_method_call} and @code{build_user_type_conversion_1} to decide
+if a particular constructor should be used as a candidate for conversions.
+
 @end itemize
 
 @node Glossary, Macros, Implementation Specifics, Top