On Thu, Apr 16, 2009 at 09:50:31PM -0400, Antoine Tremblay wrote:
> debugger invoked on a SB-INT:SIMPLE-PROGRAM-ERROR in thread #<THREAD
> "initial thread" RUNNING {100266AA61}>:
> attempt to add the method
> #<STANDARD-METHOD NIL (#<STANDARD-CLASS ELEPHANT-STORE>
> #<BUILT-IN-CLASS T>) {1003B86731}>
> to the generic function
> #<STANDARD-GENERIC-FUNCTION PERSIST-OBJECT (2)>;
> but the method and generic function differ in whether they accept
> &REST or &KEY arguments.
>
>
> Seems like an error in elephant.lisp ?
>
> Any ideas ?
Yes. I recently changed the signature of PERSIST-OBJECT and made a
mistake in adapting the Elephant backend to it.
I will check this, correct the problem and let you know.
> Btw if I may ask , I sometimes get these weird compilations issues that are
> solved with a retry ? Is that normal ?
That sounds weird indeed.
> how can compilation be solved by retrying ?
It works if you do something before that makes the retry work.
Example:
TOPLEVEL> (slot-value obj 'foo)
ERROR: slot FOO is unbound in OBJ
ERROR> (setf (slot-value obj 'foo) 5)
ERROR> (invoke-restart 'retry)
But it doesn't make sense in general to use RETRY when nothing has
changed.
> hehe maybe it's my c/cpp experience blinding me but I find this extremely
> weird if anyone care to comment on this ?
Another caveat: the ACCEPT restart is similar in that it is offered to
you in a lot of places but is useful only in a few (mostly when dealing
with warnings).
Leslie
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"weblocks" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/weblocks?hl=en
-~----------~----~----~----~------~----~------~--~---
