What is the best thing to remember about programming in C++?

Question

For example, "Be careful with null pointers."

Answer 1

Memory Handling.
Whatever memory space you occupy by instantiating the objects should be released after your use.
Type Casting should also be taken care.

Answer 2

If an object contains a [private] pointer which dynamically allocates memory, such as new, you MUST either declare the copy constructor, assignment operator and possibly delete (especially if the memory is allocated in the constructor), or you must make the copy constructor and assignment operator private.

If you don't take control of these, the C++ compiler will create default ones for you, and they will do shallow copies only. This will cause you many problems, because objects will end up with internal dangling references, and when referenced, the code will core dump with segmentation violation.

Answer 3

That OOP/OOA has produced numerous failed project and caused a general maintenance nightmare for the software world because so many people don't really understand how to do it right.

Don't let the puritans force you into hard core OOP. Functional is easier to troubleshoot and debug.

Answer 4

depends how new you are to programming-if you're new, it would probably be which way the "carrots" go, when you're dealing with cout and cin...
cout << "Hello" << endl;
cin >> number;

if you're a little more advanced, it would probably be function declarations---don't write a function without declaring it first...that can cause you lots of hassle when you're trying to figure out what you did wrong:
void Function();

int main()
{
Function();
return 0;
}

void Function()
{
cout << "Hi." << endl;
}

Answer 5

Semi-colons.

Youll spend more time ripping your hair out trying to figure why the hell something isnt working to realize that you forgot a semi-colon in one line.

Answer 6

Memory handling.. typecasting, pointers.. datastructures using c++..

Answer 7

put this in a header file

#define true false

and watch the fun :)

Answer 8

handling your memory and making sure you dont have any opportunities for buffer overruns.

Answer 9

i dont know