StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7248004
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2011-08-30T18:31:02.633
FavoriteCount
0
LastActivityDate
2013-12-31T02:01:00.927
LastEditDate
2013-12-31T02:01:00.927
LastEditorUserId
482489
OwnerUserId
36723
ParentId
3772304
PostTypeId
2
Score
18
ViewCount
0
LastEditorDisplayName
text
Body
I'm going to take a wild guess and say that the <code>Simulation::GetTasks()</code> signature looks like this: <pre><code>multimap<int,Task*> GetTasks() const; </code></pre> This creates a new multimap (a copy) each time you call it. When comparing iterators, both of the <code>multimap<int,Task*></code> iterators must come from the same container; since you're getting a new copy each time you call <code>GetTasks()</code>, you violate this constraint, and this is the source of your error. You also have another problem - the temporary multimap copies are destroyed after the statement they're created in, so your iterators are invalidated instantly. You have two choices; one is to capture a copy locally and use that copy consistently: <pre><code>multimap<int,Task*> tasks = simulation->GetTasks(); multimap<int,Task*>::iterator itTasks; itTasks = tasks.begin(); while(itTasks != tasks.end()){ while (itTasks->second->GetTimeStamp() == time->GetTime()){ TaskExecute(itTasks->second,military,shalishut,args); itTasks++; } // Unit take car of vehicles time->TimeIncrease(); } </code></pre> Another is to have <code>GetTasks()</code> return a reference to a persistent multimap, ensuring the same one is used each time: <pre><code>multimap<int,Task*> &GetTasks(); </code></pre> Or a const reference: <pre><code>const multimap<int,Task*> &GetTasks() const; </code></pre> This has the advantage of avoiding the (potentially large) overhead of copying the <code>multimap</code>. Note that using a const reference requires using <code>const_iterator</code>s to step through the multimap. I would recommend defining both const and non-const accessors (C++ will pick the right one based on if the <code>Simulation</code> pointer or reference is const), unless you want to disallow direct modification of the underlying <code>multimap</code> entirely, in which case you can define only the <code>const</code> variant.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORunTime Error : map/set iterators incompatible
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USJustcallmeDrago
UserOwnerUserId
1. USbdonlan
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
 VTApproveEditSuggestion
CommentsPostId
1. This table or related slice is empty.

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.