Re: Metaclass & McCLIM revisited

Hi Daniel,

Yes, we will be improving the MOP conformance.

Assuming this is the code on the input-editing branch of McCLIM, then the
problem you are having with mop:standard-instance-access is caused by
initialize-instance bypassing slot-*-using-class for instance allocated slots
(as you comment in the code).  So what happens is that your allocate-instance
method sets the slots to contain dynamic variable objects but the standard
initialize-instance method then sets them back to actual values from any
initargs.

-- 
Martin Simmons
LispWorks Ltd
http://www.lispworks.com/



>>>>> On Mon, 02 Mar 2026 20:09:53 +0000, Daniel Kochmański (as daniel at turtleware dot eu) said:
> 
> Hey,
> 
> I've made the necessary changes to the metaclass used in McCLIM.
> Generally LW does not follow MOP in various regards, I had to use
> Closer MOP and still add a tweak, because LispWorks seems to overwride
> whatever is stored in mop:standard-instance-access (probably some
> optimization). That's why I had to provide "non-standard" location
> to store objects implementing thread-local values.
> 
> Are there plans for LispWorks to improve MOP conformance, or is that
> not a goal (i.e because that'd degrade the performance)?
> 
> Best regards,
> Daniel
> 
> _______________________________________________
> Lisp Hug - the mailing list for LispWorks users
> [email protected]
> http://www.lispworks.com/support/lisp-hug.html
> 

_______________________________________________
Lisp Hug - the mailing list for LispWorks users
[email protected]
http://www.lispworks.com/support/lisp-hug.html