Re: Limited initialization for non-limited types

"Eric Hughes" <eric.eh9@[EMAIL PROTECTED]
> wrote in message
news:8ce4085b-08c9-4f3b-9909-3a68b8832194@[EMAIL PROTECTED]
> On Mar 28, 12:56 am, "Randy Brukardt" <ra...@[EMAIL PROTECTED]
> 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.