There are (more or less) substitutes for it, some of which are more portable as well.

You can just run your program via the command line/prompt, as you should do in the first place.

The need for it disappears if your program is not even meant to be run from the command line/prompt.

Originally Posted by Bjarne Stroustrup (2000-10-14)

I get maybe two dozen requests for help with some sort of programming or design problem every day. Most have more sense than to send me hundreds of lines of code. If they do, I ask them to find the smallest example that exhibits the problem and send me that. Mostly, they then find the error themselves. "Finding the smallest program that demonstrates the error" is a powerful debugging tool.

Well, if the examiner insists, then go ahead and do so, but note that the examiner is misguided.

Originally Posted by Bjarne Stroustrup (2000-10-14)

I get maybe two dozen requests for help with some sort of programming or design problem every day. Most have more sense than to send me hundreds of lines of code. If they do, I ask them to find the smallest example that exhibits the problem and send me that. Mostly, they then find the error themselves. "Finding the smallest program that demonstrates the error" is a powerful debugging tool.

In that case I must advise you that your teachers are not just misguided, but terribly ignorant, possibly even incompetent. If this is a private course, you would be better off dropping it.

Originally Posted by Bjarne Stroustrup (2000-10-14)

I get maybe two dozen requests for help with some sort of programming or design problem every day. Most have more sense than to send me hundreds of lines of code. If they do, I ask them to find the smallest example that exhibits the problem and send me that. Mostly, they then find the error themselves. "Finding the smallest program that demonstrates the error" is a powerful debugging tool.

its a subject in school.And the teacher comes for half an hour one day before the exam and completes the course.If it isnt completed,then its self study.Thats the case this time,so that is exactly why im sitting online surfing tutorials.

In English, post-increment makes a copy of the object with the old value, does the operation, and returns the copy. Pre-increment simply does the operation and returns a reference to the object. So it depends entirely on whether you need the initial value, most of the time. If copying the object is a performance bottleneck, than you know what to avoid...

We actually have a tutorial section on this site. It is not much, some of it is outdated, but at least it is something. In particular, check out the tutorial on if statements. At the bottom it has something to say about the logical operators (or what it calls boolean operators).

Originally Posted by Bjarne Stroustrup (2000-10-14)

I get maybe two dozen requests for help with some sort of programming or design problem every day. Most have more sense than to send me hundreds of lines of code. If they do, I ask them to find the smallest example that exhibits the problem and send me that. Mostly, they then find the error themselves. "Finding the smallest program that demonstrates the error" is a powerful debugging tool.

oh thanks!Actually i am new to C++ programming.i am a student,and we have a test tomorrow.The examiner cuts marks if you dont put in system("PAUSE")

I bet what the examiner is actually requring is that there are pauses in the execution of your code, more so than actually using system("PAUSE"). I betcha I can hack into your computer if you keep using that, and I am not turning to the dark side on anyone here... I am simply pointing out that your programs have an easily exploited security breach in them. Several times per execution, in fact.