[elephant-devel] slot-exists-p / slot-exists-p-using-class

[Ian Eslick]

I agree with Waldo.  Since 0.6.0 is a significant re-organization as
well as a new feature release with known problems, then logically it is
more of a release candidate and that designation will set people's
expectation.  (For example, I'm sure there are also problems with MCL
also as it hasn't been tested on that platform yet.) 

I vote to release 0.6.0 when we get the test suite to pass and the new
docs and tutorial completed.  In the meantime I think it's perfectly
fine to make rc1 available as part of an extended release process. 
Anyone who really wants to use the new features can pitch in some time
to find the remaining bug or two (Andrew has volunteered to take a look
at the MOP bug in the next day or two) and I'm sure one of us will get
around to it in the coming weeks. 

Cheers,
Ian

Robert L. Read wrote:
> Well, Ian and I are both exhausted (metaphorically.)
>
> It is a rare project that does not release with known bugs.
>
> But 0.6.0.rc1 can serve as well as 0.6.0 for most people, so
> I don't mind using that name --- but I will make a tar file of it,
> for the convenience of a hypothetic new user.  If they choose
> not to use class-indexing, they will not experience the known
> bugs; it is the unknown once that will be the problem.
>
> But we do have a solid test suite, relatively speaking.
>
> On Wed, 2006-02-22 at 23:01 -0500, Waldo Rubinstein wrote:
>> How about releasing 0.6.0.rc1 instead? It just doesn't fly well with
>> me the fact that a new release is coming out with known bugs. I
>> understand your point. The question is, like Ian asked, is it worth
>> fixing this bug or re-engineering to closer-to-mop.
>>
>>
>> - Waldo
>>
>> On Feb 22, 2006, at 10:43 PM, Robert L. Read wrote:
>>
>>> Thanks for this large and excellent body of work, Ian.
>>>
>>> I agree that we should use closer-to-mop.
>>>
>>> However, I am tempted to release 0.6.0 even in the presence of these
>>> bugs,
>>> as all of them concern the new functionality that you have added.  I
>>> am pretty
>>> confident 0.6.0 represents no regression from previous releases, and
>>> certainly
>>> is better in other ways.
>>>
>>> On Wed, 2006-02-22 at 17:28 -0500, Ian Eslick wrote:
>>>> These do not appear to be properly implemented for persistent slots on
>>>> any platform.  This may be part of the problem that Andrew, Robert and I
>>>> are looking at.  It should be easy to add, but I don't understand why
>>>> it's not failing.
>>>>
>>>> I also found a couple of small problems I introduced into the tests
>>>> accidentally while exploring these bugs.  I have fixed these in my
>>>> latest checkin.  If you're working on these bugs, please update:
>>>>
>>>> My full status as of this checkin is:
>>>>
>>>> Mac OS X 10.4 / ACL 8.0 / BDB -
>>>>     Backend: Green 
>>>>     Migration: Green
>>>> Mac OS X 10.4 / ACL 8.0 / SQL -
>>>>     Backend:
>>>>     Fails: INDEXING-CHANGE-CLASS (fails due to get-instances-by-value
>>>> returning 0 instead of 1 instance)
>>>>     Fails: INDEXING-REDEF-CLASS (fails due to get-instances-by-value
>>>> returns 2 instead of 1 instance)
>>>>     Migration:
>>>>     Fails: MIGRATE-IPCLASS (fails due to get-instances-by-value
>>>> returning 2 instead of 1)
>>>> Mac OS X 10.4 / SBCL 8.0 / BDB
>>>>     Backend:
>>>>     Fails: INDEXING-REDEF-CLASS (slot not found bug discussed in earlier
>>>> e-mail)
>>>>     Migration: Green
>>>> Mac OS X 10.4 / SBCL 8.0 / SQL
>>>>     Backend:
>>>>     Fails: INDEXING-REDEF-CLASS (slot not found bug discussed in earlier
>>>> e-mail)
>>>>     Migration:
>>>>     Fails: MIGRATE-IPCLASS (fails due to get-instances-by-value
>>>> returning 2 instead of 1)
>>>>
>>>> I'm beginning to think that porting over to a MOP compatibility layer
>>>> (like closer-to-mop) may be a better course than to continue to patch
>>>> the current system if no one can find this with a little more effort.  I
>>>> don't have time for at least two weeks to look at this.  I will be
>>>> available to answer questions, but not for any significant debugging or
>>>> development.
>>>>
>>>> Ian
>>>> _______________________________________________
>>>> elephant-devel site list
>>>> elephant-devel at common-lisp.net <mailto:elephant-devel at common-lisp.net>
>>>> http://common-lisp.net/mailman/listinfo/elephant-devel
>>>>         
>>> _______________________________________________
>>> elephant-devel site list
>>> elephant-devel at common-lisp.net <mailto:elephant-devel at common-lisp.net>
>>> http://common-lisp.net/mailman/listinfo/elephant-devel
>>
>>
>> _______________________________________________
>> elephant-devel site list
>> elephant-devel at common-lisp.net <mailto:elephant-devel at common-lisp.net>
>> http://common-lisp.net/mailman/listinfo/elephant-devel
>>