From: JK Victor <johnkvictor@...>
Date: 2011-05-19T08:50:54+09:00
Subject: Re: Manual Memory Management and Automatic Garbage Collection

Tridib Bandopadhyay wrote in post #999550:
> So I
> was thinking of not letting the GC to come and free memory every time
> for small objects,Stopping the code. So I just want to check if it can
> be helpful or not...

Ruby has a very primitive conservative GC -- it just scans the stack 
looking for pointers. If you are a time traveler from the 1950s then 
Ruby's GC might be an interesting study.

In any case it would be easy to fool Ruby's GC, if that's what you wish: 
allocate a pointer and hide data behind the pointer. The GC won't see 
pointers which aren't on the stack. You can manage that GC-concealed 
data however you like.

-- 
Posted via http://www.ruby-forum.com/.