[wxCL-devel] Problem with getting started

[Benjamin T. <ben...@we...>]

Hi!
I just got to know about this interesting project via comp.lang.lisp and 
tried out the 1.3 alpha under windows+acl+slime to evaluate the option 
of using it for a Go-server client.

When trying out the buttons.lisp example, I always get the following 
error when clicking the button:

Attempt to call WXCL::CFFI-OBJECT-POINTER which is defined as a macro.
   [Condition of type UNDEFINED-FUNCTION]

Restarts:
  0: [RETRY] retry the load of c:/teuber/libs/wxcl/examples/button
  1: [SKIP] skip loading c:/teuber/libs/wxcl/examples/button
  2: [RECOMPILE-DUE-TO-INCOMPATIBLE-FASL] recompile 
c:\teuber\libs\wxcl\examples\button.lisp
  3: [ABORT] Abort handling SLIME request.
  4: [ABORT] Abort entirely from this (lisp) process.

Backtrace:
  0: (SWANK::DEBUG-IN-EMACS #<UNDEFINED-FUNCTION @ #x20cbc5da>)
  1: (SWANK:SWANK-DEBUGGER-HOOK #<UNDEFINED-FUNCTION @ #x20cbc5da> 
#<Function SWANK-DEBUGGER-HOOK>)
  2: (ERROR UNDEFINED-FUNCTION :NAME WXCL::CFFI-OBJECT-POINTER 
:FORMAT-CONTROL "Attempt to call ~s which is defined as a macro." 
:FORMAT-ARGUMENTS (WXCL::CFFI-OBJECT-POINTER))
  3: (WXCL:MESSAGE-BOX "You clicked me" :CAPTION "Response")
  4: (BTN-RESPONDER-FUNCTION 201971600)
  5: (CFFI-CALLBACKS::|WXCL::HANDLE-EVENTS| :UNKNOWN)
  6: (WXCL:START-APP #<Function INIT-FUNC>)

It looks like wxcl:message-box gets compiled before the macro 
cffi-object-pointer is known. Any ideas how to resolve this?

Regards,
Ben