Custom Query (1030 matches)

(defcallback foo (:double-float a 
                  :double-float b 
                  :double-float c 
                  :double-float d 
                  :double-float e
                  :double-float f
                  :double-float g 
                  :double-float)
  (format t "~&~s" (list a b c d e f g))
  (+ a b c d e f g))

(ff-call foo :double-float 1.0d0 :double-float 2.0d0 :double-float 3.0d0 :double-float 4.0d0 :double-float 5.0d0 :double-float 6.0d0 :double-float 7.0d0 :double-float) 

prints and returns:

(1.0D0 2.0D0 3.0D0 4.0D0 1.398752D-316 0.0D0 1.3987457D-316)
10.0D0

I'm fairly sure that the caller's putting arguments (after the first 4) in the wrong place (e.g., that the callback's right and the bug's in FF-CALL.)

In a Clozure CL.app built from the event-ide branch:

1. Open a file of Lisp text. Select a range of text
2. Switch to a Listener window
3. Eval uate some form that causes a backtrace
4. Switch back to the editor window

At this point, if the problem has manifested, clicking in the buffer fails to cause the window to update its selection correctly. Typing in the buffer *may* cause the display to return to normal, or it may display a Hemlock error dialog (the "sky is falling" dialog). Generally, some combination of inserting and deleting text seems to eventually cause the window display and event-handling to return to normal.

In a Clozure CL.app built from the event-ide branch:

1. Open a file of Lisp text. Select a range of text
2. Switch to a Listener window
3. Eval uate some form that causes a backtrace
4. Switch back to the editor window

At this point, if the problem has manifested, clicking in the buffer fails to cause the window to update its selection correctly. Typing in the buffer *may* cause the display to return to normal, or it may display a Hemlock error dialog (the "sky is falling" dialog). Generally, some combination of inserting and deleting text seems to eventually cause the window display and event-handling to return to normal.