Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!ucsd!sdcsvax!ucsdhub!hp-sdd!hplabs!hp-pcd!hplsla!jima
From: jima@hplsla.HP.COM (Jim Adcock)
Newsgroups: comp.lang.c++
Subject: Re: Garbage Collection
Message-ID: <6590077@hplsla.HP.COM>
Date: 5 Dec 88 18:49:34 GMT
References: <5422@polya.Stanford.EDU>
Organization: HP Lake Stevens, WA
Lines: 11

Can't this be reasonably handled using parameterized classes 
and multiple inheritence?

-- The problem I have with garbage collection built into the
language is that it assumes that one scheme for all classes
will be good enough -- which is not my experience.

Even with a compile time option, you have an all or none 
schenerio, which is going to force users of C++ to either
buy into your version of garbage collection / memory management,
or avoid using any libraries based on your scheme.