[DGD]forced compile of auto object?

[Kevin N. Carpenter]

Actually, my object database IS in the driver object for just this reason.
I couldn't see any other way to capture those first references otherwise,
and I hate having to hard code exception list <grin>.

Thanks.

Kevin C.

-----Original Message-----
From: dgd-admin at list.imaginary.com
[mailto:dgd-admin at list.imaginary.com]On Behalf Of Par Winzell
Sent: Wednesday, March 22, 2000 7:20 PM
To: dgd at list.imaginary.com
Subject: Re: [DGD]forced compile of auto object?


 > Is there any downside to forcing a compile via compile_object() of the
auto
 > object within the driver initialization code?  Since the driver's
 > inherit_program() function isn't called for the auto object, my object
 > tracking routine never sees that object.  If I forced a compile, my
 > compile_object() redefinition would catch it.

Unless you've put your object database code in the driver object, I don't
see how the database can be compiled and activated before the auto object
is compiled -- since the auto object is always automatically inherited.
You can't recompile it either, once it's been inherited.

Since I use the kernel library and my object database is in ~System, there
is a fair number (10 or so) of programs that are compiled before my db code
ever gets initialized. But, since ~System is allowed to know about /kernel,
having an explicit list of those dependencies is not such a tragedy.

If you -really- want to avoid such a dependency list, I suppose you could
compile the object database from the driver object, activate it, destruct
the auto object, then recompile the object database...

Par

List config page:  http://list.imaginary.com/mailman/listinfo/dgd


List config page:  http://list.imaginary.com/mailman/listinfo/dgd