StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8123888
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
6
CommunityOwnedDate
CreationDate
2011-11-14T15:30:24.717
FavoriteCount
0
LastActivityDate
2011-11-14T15:52:27.717
LastEditDate
2011-11-14T15:52:27.717
LastEditorUserId
600135
OwnerUserId
600135
ParentId
8100492
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
When we call these two lines: <pre><code>TemplateClass<TemplateClass<EmptyClass> > c; TemplateClass<std::string>::static_method(c); </code></pre> then the type argument U is the type of the object c: <pre><code>TemplateClass<TemplateClass<EmptyClass> > </code></pre> Let's leave <code>static_method</code>, and do an experiment: <pre><code>#include <iostream> #include <typeinfo.h> using namespace std; template<typename T> class TemplateClass : public T { public: void method(int i) { cout < > u; u.method(1); u.TemplateClass::method(2); u.TemplateClass<EmptyClass>::method(3); u.TemplateClass<TemplateClass<EmptyClass> >::method(4); } </code></pre> The output is: <pre><code>1: class TemplateClass<class TemplateClass<class EmptyClass> > 2: class TemplateClass<class TemplateClass<class EmptyClass> > 3: class TemplateClass<class EmptyClass> 4: class TemplateClass<class TemplateClass<class EmptyClass> > </code></pre> In all four cases (and inside <code>static_method</code>) we call <code>TemplateClass<T>::method</code>, and the type name given between <code>u.</code> and <code>::</code> will give the actual type T: <ul> <li>Case #1 is the default, here T is given by the declaration of u. </li> <li>Case #4 is also trivial.</li> <li>Case #2 looks as if the compiler should have guessed the type argument of TemplateClass, which is trivially the one given in the declaration of u.</li> <li>Case #3 is very interesting. I guess function type casting happened here, from <code>TemplateClass<TemplateClass<EmptyClass> >::method</code> to <code>TemplateClass<EmptyClass>::method</code>.</li> </ul> I don't know whether this behavior is part of the C++ standard. EDIT: Actually case #3 is not casting, these are qualified names. So in conclusion, Clang is not aware of this qualification syntax, while both GCC and Visual C++ 2010 are.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAmbiguous member access expression: is Clang rejecting valid code?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USkol
UserOwnerUserId
1. USkol
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COWhich compiler did the output come from?
 singulars
 PostPostId
 PO
 UserUserId
 USPer
2. COActually case #3 is not casting, these are **qualified names**.
 singulars
 PostPostId
 PO
 UserUserId
 USkol
3. CO@Per Visual C++ 2010
 singulars
 PostPostId
 PO
 UserUserId
 USkol

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.