Jump to content

View more

Image of the Day

Boxes as reward for our ranking mode. ヾ(☆▽☆)
#indiedev #gamedev #gameart #screenshotsaturday https://t.co/ALF1InmM7K
IOTD | Top Screenshots

The latest, straight to your Inbox.

Subscribe to GameDev.net Direct to receive the latest updates and exclusive content.


Sign up now

Moving from Java to c++

4: Adsense

Old topic!

Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.


  • You cannot reply to this topic
21 replies to this topic

#21 lride   Members   

663
Like
0Likes
Like

Posted 02 November 2012 - 02:52 PM

Brace yourself for the horrors of memory management


Nowdays, we got good memory leak detectors that point out the actual location in your source code where the memory leak occured.
My favorite is Visual Leak Detector(compatible with VS 08, 10 and 12)
I do not think the manual memory management is going to be a "horror".
An invisible text.

#22 joew   Members   

4336
Like
1Likes
Like

Posted 02 November 2012 - 07:14 PM

I do not think the manual memory management is going to be a "horror".

I agree as realistically if using C++11 and RAII properly there shouldn't be much worry about memory management/leaks at all. As mentioned above there are also good tools for tracking things down if needed.. although using std::unique_ptr, std::shared_ptr, and std::weak_ptr effectively really makes things quite simple. I actually find memory management easier in C++11 than using garbage collected languages as the pointer classes are safe and I still control their actual point of destruction... imo it's a win-win.

Edited by joew, 02 November 2012 - 07:15 PM.





Old topic!

Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.