StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19510076
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-10-22T06:01:51.137
FavoriteCount
0
LastActivityDate
2013-10-22T07:35:29.800
LastEditDate
2013-10-22T07:35:29.800
LastEditorUserId
767516
OwnerUserId
767516
ParentId
19508639
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
can't you define your getSum() function in the stack implementation? Or is there any restrictions? Sol-1: <pre><code>template <class Object> Object Stack<Object>::getSum( ) { Object sum = 0; // or memset or other stuffs StackNode<Object> * node = topNode; while (node != NULL) { sum += node->getElement(); node = node->getNext(); } return sum; } </code></pre> As Gary mentioned you can also improve efficiency by caching the sum value every time you push or pop (i,e stack is changed) Sol-2: Add a member property which will denote the sum (e,g - sum) <pre><code>template <class Object> Stack<Object>::Stack() { topNode = NULL; this->sum = 0; // initialize or new object } </code></pre> update the sum whenever a object is pushed <pre><code>template <class Object> void Stack<Object>::push( const Object& data ) { StackNode<Object>* newNode = new StackNode<Object>( data, topNode ); topNode = newNode; this->sum = this->sum + data; } </code></pre> same update goes for pop() whenever an object is removed <pre><code>template <class Object> void Stack<Object>::pop() { if (isEmpty()) { throw EmptyStack(); } StackNode<Object> *oldTop = topNode; topNode = topNode->getNext(); this->sum = this->sum - oldTop->getElement(); delete oldTop; } </code></pre> now your last function getSum() <pre><code>template <class Object> Object Stack<Object>::getSum( ) { return this->sum; } </code></pre> Sol-1 has O(N) = N cost while Sol-2 has O(N) = 1 Now you should be able to use pStack->objectIsEven(pStack->getSum()); I think you aren't required to be concerned about threading in your stack implementation otherwise you should use some kind of synchronization mechanism while insert/delete operation to make the stack consistent. Hope this helps. regards,
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAdd every value in stack
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USfadedreamz
UserOwnerUserId
1. USfadedreamz
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POAdd every value in stack
 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
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.