<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Mar 22, 2010, at 5:13 PM, Douglas Gregor wrote:</div><blockquote type="cite"><div><font class="Apple-style-span" color="#000000"><br></font><br>... and after talking with John for a bit, we're starting to like the following scheme:<br><br>DependentQualifiedNameType: captures all qualified types with dependent names, including elaborated-type-specifiers (class/struct/union/enum), typename-specifiers (typename), and implied dependent name types (X<T>::type as a base class).<br><br>ElaboratedType: captures all elaborated-type-specifiers (class/struct/union/enum), typename-specifiers (typename), and qualified names (no other adornment) where we were able to look up the type. These nodes can have an optional NestedNameSpecifier, and will always have either a class/struct/union/enum keyword or a nested-name-specifier.<br></div></blockquote></div><br><div>Enea or Abramo, are either of you working on this? If not, I'll go ahead and implement this change.</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- Doug</div></body></html>