>>23
Most garbage collected systems allow a way (an easy or a hard one) to turn of garbage collection. I don't really consider that a feature. If you need it, there's something wrong with your language implementation.
The only time I've ever needed such a feature was when I wrote a performance-critical routine in Ruby (yeah, that it every bit as ridiculous as it sounds). I read everything about Ruby's garbage collection, and tuned my inner loop to match with its inner workings; force-feeding it with efficiently packed data. As a result, everything was still slow as fuck (and I wasn't even on Rails!). Then I realized Ruby offered a convenient way to stop garbage colllection, and used it. To say ``the code ran fucking fast'' would be an understatement. I can't believe what a fucking pile of crap the Ruby garbage collector is.
tl;dr: Most language implementations provide it in some form. If you actually really do need to do it, change your implementation or language, FAST.