On 05/06/07, Luke Crook <[EMAIL PROTECTED]> wrote: > Brad Beveridge <[EMAIL PROTECTED]> writes: > > > > > Good luck with getting Cocoahelper working. If I were you, I'd look > > at how other non-C languages (ie Python and Pygame) manage it. > > Brad, > > I thought that Cocoahelper was working at one stage?
I guess it depends on your definition of "working". I suspect that when I submitted it I ran single threaded SBCL OS X Intel, and I did not use Slime. I've just tested doing (require 'lispbuilder-sdl) (require 'lispbuilder-sdl-examples) (require 'lispbuilder-sdl-cocoahelper) (lispbuilder-sdl-examples:recursive-rects) In SBCL's REPL. This works in both console & Slime. Trying to break with C-c C-b causes SBCL to spit out in the *inferior-lisp* buffer: "fatal error encountered in SBCL pid 314(tid 2684407776): blockable signal 1 not blocked LDB monitor ldb>" So, you can use it, but the Slime debugger is pretty broken. This with Slime not using threads for communication. So, yes, cocoahelper works (with SBCL) - but it is not a particularly friendly environment for Slime. Cheers Brad _______________________________________________ application-builder mailing list [email protected] http://www.lispniks.com/mailman/listinfo/application-builder
