Garbage collection working improperly?

[Aahz]

In article <bplcb9$f4g$1 at reader2.nmix.net>,
Jay O'Connor  <joconnor at cybermesa.com> wrote:
>
>I kinda like VisualWorks Smalltalk's approach.  It uses a system whereby 
>new objects are scavenged aggresivly and objects that survive the 
>scavenger are moved to a different memory space that is not GC'ed nearly 
>as much.  (New objects tend to have short lives..objects that survive 
>several generations of scavenging tend to live longer) When it's memory 
>reaches a threshold, it makes a decision as to whether to either request 
>more from the OS or  to GC the old object memory space in an  attempt to 
>free more memory.  The nice part is that you can configure a. how much 
>memory it starts with b. at what point the threshold is set for and 
>c.the weighting of the algorithim to determine whether to GC or allocate

Python does the same thing -- you just can't configure it as much.
-- 
Aahz (aahz at pythoncraft.com)           <*>         http://www.pythoncraft.com/

Weinberg's Second Law: If builders built buildings the way programmers wrote 
programs, then the first woodpecker that came along would destroy civilization.