Path: utzoo!utgpu!watmath!clyde!att!ucbvax!hplabs!hp-pcd!hplsla!jima From: jima@hplsla.HP.COM (Jim Adcock) Newsgroups: comp.lang.c++ Subject: Re: Garbage Collection Message-ID: <6590081@hplsla.HP.COM> Date: 6 Dec 88 18:09:42 GMT References: <5422@polya.Stanford.EDU> Organization: HP Lake Stevens, WA Lines: 14 My concerns with GarbageCollection are 1) What algorithm are you guys talking about, so we can discuss the shortcomings of that particular method? 2) Show me a GarbageCollection algorithm that isn't going to cost me in my classes that don't need it. Again, the argument that "Well, you can always turn garbage collection off if you don't want to use it" would seem to me to force all libraries into one of two categories that can't be mixed: 1) libraries that use garbage collection 2) libraries that don't use garbage collection. So then you don't really have one language anymore, you have two. (If you don't have hard realtime constraints, why not use Smalltalk :-)