StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
659447
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2009-03-18T18:03:11.380
FavoriteCount
0
LastActivityDate
2009-03-18T18:10:29.413
LastEditDate
2009-03-18T18:10:29.413
LastEditorUserId
33686
OwnerUserId
33686
ParentId
659231
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
eJames
text
Body
The reason for the compiler error is a circular dependency. Each of your operator=() functions require knowledge of the operator=() function inside the other class, so no matter which order you define your classes in, there will always be an error. Here is one way to sort it out. It isn't very elegant, but it will do what you want: <pre><code>class A; class B; A & set_equal(A & a, const B & b); B & set_equal(B & a, const A & a); class A { private: int x; public: A & operator=(const B & b) { return set_equal(*this, b); } friend B & set_equal(B & b, const A & a); friend A & set_equal(A & a, const B & b); }; class B { private: int y; public: B & operator=(const A & a) { return set_equal(*this, a); } friend A & set_equal(A & a, const B & b); friend B & set_equal(B & b, const A & a); }; A & set_equal(A & a, const B & b) { a.x = b.y; return a; } B & set_equal(B & b, const A & a) { b.y = a.x; return b; } </code></pre> You may also be able to solve this problem with inheritance. edit: here is an example using inheritance. This will work if the copying procedure only needs access to some common data shared by both A and B, which would seem likely if the = operator is to have any meaning at all. <pre><code>class A; class B; class common { protected: int x; void copyFrom(const common & c) { x = c.x; } }; class A : public common { public: A & operator=(const common & c) { copyFrom(c); return *this; } }; class B : public common { public: B & operator=(const common & c) { copyFrom(c); return *this; } }; </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCrossing assignment operators?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USe.James
UserOwnerUserId
1. USe.James
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POCrossing assignment operators?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
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
 VTDownMod
CommentsPostId
1. CO@recent downvoter: What was my error?
 singulars
 PostPostId
 PO
 UserUserId
 USe.James

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.