Re: Limited initialization for non-limited types

On Mar 28, 3:53 pm, "Randy Brukardt" <ra...@[EMAIL PROTECTED]
> 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