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-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,4103f02f9e6c4df2 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-02-15 12:04:24 PST Path: supernews.google.com!sn-xit-02!sn-xit-01!supernews.com!newshub2.rdc1.sfba.home.com!news.home.com!newsfeed.mesh.ad.jp!newsranger.com!www.newsranger.com!not-for-mail Newsgroups: comp.lang.ada From: Ted Dennison Sender: usenet@www.newsranger.com References: Subject: Re: RE: Ada 0y wish list: Message-ID: Date: Thu, 15 Feb 2001 20:03:35 GMT NNTP-Posting-Host: 127.0.0.1 X-Complaints-To: abuse@newsranger.com X-Trace: www.newsranger.com 982267415 127.0.0.1 (Thu, 15 Feb 2001 15:03:35 EST) NNTP-Posting-Date: Thu, 15 Feb 2001 15:03:35 EST Organization: http://www.newsranger.com Xref: supernews.google.com comp.lang.ada:5283 Date: 2001-02-15T20:03:35+00:00 List-Id: In article , Beard, Frank says... > >I disagree. If the compiler treated the deferred type >as a "by reference" type then there wouldn't be a problem. >It would be similar to an access type without the requirement >of allocation/deallocation, null checks, etc. > >When a variable of type B is declared, the compiler will >always pass it by reference (by address), which is the >equivalent of passing an access type. But passing parameters isn't the only issue. You also have to generate code for allocating stack space for objects of that type. In extreme cases, you might even need to create an array type or do something else relatively static based on the type's 'size. How are you going to do that without needing that code to be regenerated whenever the source file containing the definition of the object's size is recompiled? --- T.E.D. homepage - http://www.telepath.com/dennison/Ted/TED.html home email - mailto:dennison@telepath.com