Modern C++: don't use f*cking pointers.

by Ideka • 13 years ago

14 7 13 years ago

adamnemecek2• 13 years ago

Good thing that the author provided such an exhaustive list of arguments supporting his opinions. Oh wait. Between using pointers and the standard library, I think that I will stick with pointers.

tqh2• 13 years ago

To me at least build_new_object example seems horribly wrong: If you allocate the object on the stack and then returns it, it will go out of scope with the function, and the memory overwritten with next stack usage. Or does modern C++ do some magic nowadays?

adamnemecek2• 13 years ago

I don't think that it even can do anything about that. It will just go out of scope and that's that.

sixbrx• 13 years ago

No it will use a copy or move constructor to return the object by value, no problem there. Notice the value is being returned, not a pointer to the value.

xyzzy1232• 13 years ago

Generally this is reasonable advice although I would not have stated it quite so emphatically.

Most of the time when I type * in my own C++ code, what I mean is:

    "hey! this is an in/out parameter!".

Modern C++: don't use f*cking pointers.

Related Stories