You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A few related minor issues in Activity 2.5.2.2., section 2.5.2.:
The question asks what cout << *ptrN << endl; would print and marks the correct answer as varPtr: 50, but that is not technically correct. It would only print 50. If the intention is to print varPtr: 50 the statement should be cout << "varPtr: " << *ptrN << endl;. As it is, option e is actually the (technically) correct one (although marking it as such would make this a bit of a trick question). Also, varPtr seems to be an older name of the pointer in the example, should probably be updated to ptrN now.
The feedback for answer a is inconsistent with the answer itself, after the value was changed from 100 to 9 in commit 8ab95eb.
The feedback for answer c is also inconsistent with the answer. Judging the intention by the feedback text, the answer should be updated to be 59, rather than 150.
The question itself could be a little clearer about where this extra code should be inserted. Clearly, it needs to be inserted after line 7, for example between lines 7 and 8, rather than "into line 7-8", which could mean the same thing but is a little vague.
The text was updated successfully, but these errors were encountered:
A few related minor issues in Activity 2.5.2.2., section 2.5.2.:
The question asks what
cout << *ptrN << endl;
would print and marks the correct answer asvarPtr: 50
, but that is not technically correct. It would only print50
. If the intention is to printvarPtr: 50
the statement should becout << "varPtr: " << *ptrN << endl;
. As it is, option e is actually the (technically) correct one (although marking it as such would make this a bit of a trick question). Also,varPtr
seems to be an older name of the pointer in the example, should probably be updated toptrN
now.The feedback for answer a is inconsistent with the answer itself, after the value was changed from 100 to 9 in commit 8ab95eb.
The feedback for answer c is also inconsistent with the answer. Judging the intention by the feedback text, the answer should be updated to be
59
, rather than150
.The question itself could be a little clearer about where this extra code should be inserted. Clearly, it needs to be inserted after line 7, for example between lines 7 and 8, rather than "into line 7-8", which could mean the same thing but is a little vague.
The text was updated successfully, but these errors were encountered: