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=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM autolearn=no 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!postnews.google.com!s37g2000prg.googlegroups.com!not-for-mail From: Eric Hughes Newsgroups: comp.lang.ada Subject: Re: Limited initialization for non-limited types Date: Fri, 28 Mar 2008 16:37:04 -0700 (PDT) Organization: http://groups.google.com Message-ID: <7bf04295-7e24-47da-b1c9-cbc67aa366d8@s37g2000prg.googlegroups.com> References: <05336885-5b45-4b2d-b27c-733c2002ca58@s13g2000prd.googlegroups.com> <8ce4085b-08c9-4f3b-9909-3a68b8832194@s8g2000prg.googlegroups.com> NNTP-Posting-Host: 166.70.57.218 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: posting.google.com 1206747424 31479 127.0.0.1 (28 Mar 2008 23:37:04 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Fri, 28 Mar 2008 23:37:04 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: s37g2000prg.googlegroups.com; posting-host=166.70.57.218; posting-account=5RIiTwoAAACt_Eu87gmPAJMoMTeMz-rn User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12,gzip(gfe),gzip(gfe) Xref: g2news1.google.com comp.lang.ada:20623 Date: 2008-03-28T16:37:04-07:00 List-Id: On Mar 28, 3:53 pm, "Randy Brukardt" wrote: > The other thing I was thinking was that you might be better served by > wrapping your trace object access in a (second) controlled object. I had already done that. The testing objects use both a trace and a variable name: a trace to record (interleaved) events and a name to distinguish between their disparate origins. Since the trace is shared, it needed a handle/body implementation. > You'd probably need an access > discriminant somewhere to provide access to the parent object. As of yet, I haven't needed that, since the trace is only a receiver of event entries. Eric