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, LOTS_OF_MONEY autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,87557ce53b069315 X-Google-Attributes: gid103376,public From: "Matthew Heaney" Subject: Re: meaning of "current instance" Date: 1999/11/13 Message-ID: <382e2e08_2@news1.prserv.net>#1/1 X-Deja-AN: 548334081 Content-transfer-encoding: 7bit References: Content-Type: text/plain; charset="US-ASCII" X-Complaints-To: abuse@prserv.net X-Trace: 14 Nov 1999 03:35:36 GMT, 32.101.8.144 Organization: Global Network Services - Remote Access Mail & News Services Mime-version: 1.0 Newsgroups: comp.lang.ada Date: 1999-11-13T00:00:00+00:00 List-Id: In article , tmoran@bix.com wrote: > Is there anything you can do with "current instance" that couldn't > be done (and perhaps more safely) with Initialize on a Controlled type? > I grant that ":=T'access;" is simpler, but it could be done with > Initialize. My original motivation for using type RT is tagged limited record I : Integer := Init (RT'Access); end record; instead of type RT is new Limited_Controlled with record I : Integer; end record; procedure Initialize (O : in out RT); was precisely to avoid having to use a controlled type. Controlled types are in general less efficient than non-controlled types. -- Get the FAQs about evolution and creationism.