sf::Sprite Rotation causes Crash

[Silvah]

Well, when one doesn't need to use pointers, one doesn't use new at all, does she?

The question is not "why pointers should be avoided whenever and wherever possible". I assure you that I know why and I completely agree with you in this regard. The question is: what's so bad with new (assuming one has a good reason to dynamically allocate memory)? I always thought there's nothing wrong with new itself, it's the manual deletion what should be avoided.

[Nexus]

What's wrong with, for example, the following code?

Code: [Select]

scoped_ptr<Base> ptr(someCondition ? new DerivedA(foo) : new DerivedB(bar));

The second and third operand of the conditional operator have different types, which is not allowed.

I said that manual memory management should be avoided, I explicitly listed new and delete in parentheses. I haven't spoken about new on its own, so you probably misunderstood me.

[Silvah]

The second and third operand of the conditional operator have different types, which is not allowed.

Oh well This stuff happens, let's pretend that it was only a pseudocode, or that DerivedA is a base of DerivedB, or something

I said that manual memory management should be avoided, I explicitly listed new and delete in parentheses.

I've read that "and" as "both new and delete should be avoided", but you rather meant "new together with (manual) delete should be avoided". My bad