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,efc9f994d31d0d5e X-Google-Attributes: gid103376,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news4.google.com!feeder1-2.proxad.net!proxad.net!feeder1-1.proxad.net!club-internet.fr!feedme-small.clubint.net!nuzba.szn.dk!news.jacob-sparre.dk!pnx.dk!not-for-mail From: "Randy Brukardt" Newsgroups: comp.lang.ada Subject: Re: Limited initialization for non-limited types Date: Fri, 28 Mar 2008 16:53:27 -0500 Organization: Jacob's private Usenet server Message-ID: References: <05336885-5b45-4b2d-b27c-733c2002ca58@s13g2000prd.googlegroups.com> <8ce4085b-08c9-4f3b-9909-3a68b8832194@s8g2000prg.googlegroups.com> NNTP-Posting-Host: static-69-95-181-76.mad.choiceone.net X-Trace: jacob-sparre.dk 1206741245 1241 69.95.181.76 (28 Mar 2008 21:54:05 GMT) X-Complaints-To: news@jacob-sparre.dk NNTP-Posting-Date: Fri, 28 Mar 2008 21:54:05 +0000 (UTC) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1914 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1914 Xref: g2news1.google.com comp.lang.ada:20622 Date: 2008-03-28T16:53:27-05:00 List-Id: "Eric Hughes" wrote in message news:8ce4085b-08c9-4f3b-9909-3a68b8832194@s8g2000prg.googlegroups.com... > On Mar 28, 12:56 am, "Randy Brukardt" wrote: ... > > I still think that your entire approach is wrong. I'd probably either try > > something using a mixin generic, or more likely simply with a bit debugging > > code built into the base class. > > I looked at initialization first because it's more widely applicable > outside of my immediate need, for which I think type discriminants may > work. A discriminant whose access_definition is a handle to ordinary > record seems to allow most everything I can think I need soon. Yes. The other thing I was thinking was that you might be better served by wrapping your trace object access in a (second) controlled object. That way, you can use the trace object's Initialize to do your needed setup before the call of the outer object's Initialize. You'd probably need an access discriminant somewhere to provide access to the parent object. Randy.