------- Comment #3 from igodard at pacbell dot net 2010-03-08 15:37 -------
You sure that you want to ban this? Looks like you'll just have to unban it
again. From http://en.wikipedia.org/wiki/Decltype:
In December 2008, a concern was raised to the committee by Jaakko Järvi over
the inability to use decltype to form a qualified-id,[13] which is inconsistent
with the intent that decltype(e) should be treated "as if it were a
typedef-name".[14] While commenting on the formal Committee Draft for C++0x,
the Japanese ISO member body noted that "a scope operator(::) cannot be applied
to decltype, but it should be. It would be useful in the case to obtain member
type(nested-type) from an instance as follows":[15]
vector<int> v;
decltype(v)::value_type i = 0; // int i = 0;
In September 2009, Daveed Vandevoorde proposed a wording change to correct the
issue.[16] The solution involved adding a decltype-specifier to the list of
allowed nested-name-specifiers, and changing the wording to emphasize that a
nested-name-specifier denotes a class rather than naming it.[16]
--
igodard at pacbell dot net changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|DUPLICATE |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43285
