Linked by Thom Holwerda on Mon 13th Dec 2010 19:27 UTC, submitted by lemur2
Mono Project For the most time, I've been firmly in the largest camp when it comes to the Mono debate - the 'I don't care'-camp. With patent lawsuits being hotter than Lady Gaga right now, that changed. For good reason, so it seems; while firmly in the 'ZOMG-MICROSOFT-IS-T3H-EVILL!1!!ONE!'-camp, The-Source.com investigated the five most popular Mono applications, and the conclusion is clear: all of them implement a lot of namespaces which are not covered by Microsoft's community promise thing.
Permalink for comment 453552
To read all comments associated with this story, please click here.
RE[5]: Evil Companies
by flynn on Tue 14th Dec 2010 19:41 UTC in reply to "RE[4]: Evil Companies"
flynn
Member since:
2009-03-19

Whoa, Qt does not do memory management "for you". You still have to delete just like any C++ framework.

If I recall correctly all the Qt classes take a parent pointer as a constructor argument. The parent keeps track of all it's children and deletes them when the parent gets deleted. While not the panacea of memory management, it does help a lot. For other things there are always auto_ptr and shared_ptr to ensure proper deletion when resources go out of scope.

Reply Parent Score: 2