Linked by ebasconp on Fri 10th Jun 2011 22:22 UTC
Permalink for comment 476973
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
Linked by Thom Holwerda on 04/16/13 9:29 UTC
More Features »
Sponsored Links



Member since:
2009-08-05
How do you handle cyclic references with that approach? (root-tracing GC helps a lot in handling those).
How do you suspect it performs in heavily threaded code? (you need mutexing both on the refcount and on your heap).
GC isn't the end-all-be-all, but for a lot of scenarios it works very well - and it's going to be a lot of effort emulating in C++, and won't be a full solution as long as you need to interface with legacy code.
Don't get me wrong, I'm a sucker for C++ and RAII, but it's not the only-and-best solution for all scenarios.