home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!snorkelwacker.mit.edu!ai-lab!life.ai.mit.edu!tmb
- From: tmb@arolla.idiap.ch (Thomas M. Breuel)
- Newsgroups: comp.lang.c++
- Subject: Re: Garbage Collection for C++
- Message-ID: <TMB.92Aug29175419@arolla.idiap.ch>
- Date: 29 Aug 92 21:54:19 GMT
- References: <DAVEG.92Aug17224359@synaptx.synaptics.com>
- <1992Aug20.213720.16599@microsoft.com> <boehm.714410546@siria>
- <1992Aug25.185458.10190@microsoft.com> <boehm.714847027@siria>
- Sender: news@ai.mit.edu
- Reply-To: tmb@idiap.ch
- Organization: IDIAP (Institut Dalle Molle d'Intelligence Artificielle
- Perceptive)
- Lines: 20
- In-reply-to: boehm@parc.xerox.com's message of 26 Aug 92 16:37:07 GMT
-
- In article <boehm.714847027@siria> boehm@parc.xerox.com (Hans Boehm) writes:
-
- Agreed. Support for movable objects is a good thing. But it also has
- a very substantial cost, in that lots of compilers and libraries need to be
- fixed. Some (nonportable but useful) programming paradigms break (e.g.
- hashing pointers no longer works. You need an extra counter field per
- allocated object if you want to be able to hash.) There is a cost (of
- one kind or another) in maintaining enough descriptor information.
-
- To inject some real-world data again, fragmentation can be a problem.
- I have a machine with about 200M swap space, and a program that only
- needed about half that much memory ran out of memory because of
- fragmentation.
-
- I think movable objects ultimately are very important, but, like so
- many things that are very important, support for them seems to be
- difficult to add cleanly and efficiently to the C++ programming
- language.
-
- Thomas.
-