From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,3498dd887729ed19 X-Google-Attributes: gid103376,public From: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: Garbage Collection in Ada Date: 1996/10/15 Message-ID: #1/1 X-Deja-AN: 189681246 references: <01bbb910$f1e73f60$829d6482@joy.ericsson.se> <199610132138291604607@dialup101-6-14.swipnet.se> <1996Oct13.194807.1@eisner> organization: New York University newsgroups: comp.lang.ada Date: 1996-10-15T00:00:00+00:00 List-Id: " Adding support for a storage pool that supports GC would probably be EXTREMELY low cost. Doesn't GCC already use "fat" pointers under some circumstances? All that would be needed is a pragma that indicates that a certain storage pool uses fat pointers. " I am not sure what your shouted EXTREMELY is about here. We have looked into this partial solution, and it is not at all easy to implement for all sorts of reasons, remember that you have to identify the roots. So that seems to mean that the pointers must be controlled, but even so, there are many details to this. Cyrille Comar has looked at these issues in detail, and if it was EXTREMELY easy to implement, it would have been done a long time ago!