[elephant-devel] Re: more allegro edits to avoid compiler warnings

[Andrew Blumberg]

hi andrew and robert,

 	i'm going to start trying to debug the problems reported below. 
the class updating code was intended to force a finalization before any 
access occurred (by obsoleting the instances), but obviously it isn't 
working correctly.  i'll keep you posted on my efforts to correct this 
problem.  thanks for the detailed transcript.

 								- andrew

> On Tue, 2006-01-10 at 15:15 -0800, Andrew Philpot wrote:
>
>> I left out the symptoms before.  Sorry.
>>
>> I've since gone further, and so I have a sample case that I would like
>> to show you.  I would be interested in whether this happens on other
>> platforms as well.  Again, if it comes down a question of why doesn't
>> YYY work on ACL as it does on SBCL et al, I can submit to Franz.
>>
>> Essentially, I have found that reDEFCLASSing persistent classes tends
>> to stir things up in a way that slots are no longer visible after the
>> redefinition.  Mostly by accident, I also found that explicitly
>> calling CLOS::FINALIZE-INHERITANCE after the redefinition and before
>> any use of the class usually does the right thing.
>>
>> See the attached code and transcript, abstracted from my real
>> application.  If you set the variable user::*EAGERLY-FINALIZE* to
>> non-NIL, then at COMPILE/LOAD/EVAL it will try to finalize the
>> definition (if such already exists).  I'm trying to be
>> hyperconservative about when to define things, so that's why it does
>> OPEN-STORE/CLOSE-STORE so globally before tinkering with the
>> definitions.
>>
>> #Andrew
>>
>