Re: [long answer] Re: copy-object
If the objects are not instantiated, how do you identify them?
One possibility is to have a wrapper class with one unbound slot.
All GF access this slot.
As soon a GF access the slot, the method unbound-slot is called and you can instantiate the slot with the real object.
That way creating the wrapper should be very cheap and the real object is instantiated on demand in a cost effective way.
Samir
| Eric Smith <eric3057@yahoo.com>
Sent by: owner-lisp-hug@xanalys.com 05.03.2002 01:04
|
To: lisp-hug@xanalys.com cc: Subject: Re: [long answer] Re: copy-object |
--- Espen Vestre <ev@netfonds.no> wrote:
> it's a bit difficult to understand why you'd need to
> "materialize"
> these objects at all before you actually need them,
> but if you need
> to, why not represent them as argument lists to
> make-instance?
That's an elegant solution, except that I want to be
able to invoke methods on the objects without knowing
whether they have been instantiated, such that they
would be instantiated automatically if needed.
__________________________________________________
Do You Yahoo!?
Yahoo! Sports - sign up for Fantasy Baseball
http://sports.yahoo.com