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: lars.farm@ite.mh.se (Lars Farm)
Subject: Re: Garbage Collection in Ada
Date: 1996/10/18
Message-ID: <199610182314423204049@dialup122-4-9.swipnet.se>#1/1
X-Deja-AN: 190532370
references: <01bbb910$f1e73f60$829d6482@joy.ericsson.se>
 <199610132138291604607@dialup101-6-14.swipnet.se> <1996Oct13.194807.1@eisner>
 <JSA.96Oct14174741@alexandria> <dewar.845386292@merv>
 <EACHUS.96Oct15143310@spectre.mitre.org>
 <Pine.GSO.3.93.961017160658.10939A-100000@sky.net> <dewar.845608007@merv>
organization: pv
nntp-posting-user: s-49817
newsgroups: comp.lang.ada
Date: 1996-10-18T00:00:00+00:00
List-Id: <comp.lang.ada>


Robert Dewar <dewar@merv.cs.nyu.edu> wrote:

> Hands up those who
> use 32 bit integers in your programs! Is that brittle simply because some
> Ada compilers don't have 32 bit integers? I don't think so!

Yes. Same situation in C++. Brittle enough for me to do this if I need
32-bit ints:

  class X {
    struct assert_ { char intsize[ sizeof(int) >= 4 ? 1 : 0 ]; };
    ...

The point is related to GC. There should be some portable way to detect
the presence of GC at compiletime. Ada has optional GC. I don't know Ada
enough so I ask: Is there a portable way to detect at compiletime
whether the implementation supports GC or is there not?


-- 
Lars Farm, lars.farm@ite.mh.se