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.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,c50f57c0c29b391b X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news4.google.com!news.glorb.com!newscon02.news.prodigy.com!newscon06.news.prodigy.com!prodigy.net!newsfeed-00.mathworks.com!nntp.TheWorld.com!not-for-mail From: Robert A Duff Newsgroups: comp.lang.ada Subject: Re: memory management Date: 31 May 2005 08:04:47 -0400 Organization: The World Public Access UNIX, Brookline, MA Message-ID: References: <1131064.rs72P29t4t@yahoo.com> <1226363.QsRZW1KHie@linux1.krischik.com> NNTP-Posting-Host: shell01.theworld.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: pcls4.std.com 1117541087 27398 192.74.137.71 (31 May 2005 12:04:47 GMT) X-Complaints-To: abuse@TheWorld.com NNTP-Posting-Date: Tue, 31 May 2005 12:04:47 +0000 (UTC) User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 Xref: g2news1.google.com comp.lang.ada:11209 Date: 2005-05-31T08:04:47-04:00 List-Id: Simon Wright writes: > Robert A Duff writes: > > > By the way, I believe the fat pointers used by GNAT are an option -- > > there's some way to tell it to use thin pointers for > > access-to-array. GNAT uses fat pointers (by default) only when the > > designated type is an array, or when the designated type is unknown > > to the compiler. Access-to-record, which is far more common, uses > > thin pointers. I don't know of any Ada implementation besides GNAT > > that uses fat pointers at all. > > I think that it uses fat pointers when the type concerned is > indefinite. I don't think so -- I think it's only for indefinite *arrays* (or unknown types). There's really no advantage in fat pointers for records, unless tags/discrims are separated out, which GNAT does not do. (Nor does any other compiler I know of.) > You can make it use thin pointers by specifying the 'Size of the > pointer (to be 32) or, I'm pretty sure, by pragma Convention (C); I've > sent classwide pointers via Xt client_data values using one of these > techniques. Yes, I think that's right. - Bob