On Aug 28, 12:43 am, Raymond Wiker <[email protected]> wrote:
> On Aug 27, 2009, at 18:30 , Leslie P. Polzer wrote:
>
>
>
>
>
>
>
> > Hi Eric,
>
> >> I'm running CCL 1.4 on Mac OSX (PPC), and the basic weblocks demo
> >> breaks for me out of the box. When I run (weblocks:start-weblocks) it
> >> blows up like so:
>
> >> value CCL::*NX-CURRENT-CODE-NOTE* is not of the expected type (MEMBER
> >>                                                               SETF
>
> >> LAMBDA).
>
> >> Hunchentoot runs fine on my machine – is there something going on  
> >> with
> >> weblocks here, or have I done something wrong?
>
> > Neither, I think.
>
> > This looks like a newly introduced compiler bug in CCL.
>
> > Send it to the CCL guys, maybe they can fix it right away.
>
> > If not report back here and I'll try to come up with an
> > isolated test case.
>
> Not a new error - I saw that quite some time back. I got round this by  
> the following simple patch:

Thanks Raymond, that did the trick, though I hope that won't cause
further problems in the future! Let me know if something should still
be said to the CCL folks.

Thanks again,
Eric

>
> diff -r efc83a14156b src/control-flow/dialog.lisp
> --- a/src/control-flow/dialog.lisp      Wed Jul 15 18:01:35 2009 +0200
> +++ b/src/control-flow/dialog.lisp      Thu Aug 27 18:42:41 2009 +0200
> @@ -68,7 +68,7 @@
>   'callee' answers, removes the modal interface and reactives the
>   computation. If the modal interface isn't available, automatically
>   scales down to 'do-modal' instead."
> -  (assert (stringp title))
> +  ; (assert (stringp title))
>     (if (ajax-request-p)
>         (prog2
>           (when (current-dialog)
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to