Re: CLSQL version 5.1.0 released

Kevin Raison <[email protected]>
Newsgroups gmane.lisp.clsql.general
Organization Chatsubo.net, LLC
Message-ID <[email protected]>
I am having trouble with 5.1.0, using the newest UFFI and the newest 
CFFI. See the compile error below.  It looks like the :ENCODING keyword 
is not valid for CFFI-UFFI-COMPAT:CONVERT-FROM-FOREIGN-STRING.

; file: /usr/local/lib/sbcl/site/clsql-5.1.0/uffi/clsql-uffi.lisp
; in: DEFUN CONVERT-RAW-FIELD
;     (CFFI-UFFI-COMPAT:CONVERT-FROM-FOREIGN-STRING CLSQL-UFFI::CHAR-PTR
;     :NULL-TERMINATED-P (NOT LENGTH)
;     :LENGTH LENGTH :ENCODING
;     CLSQL-UFFI::ENCODING)
; 

; caught ERROR:
;   (in macroexpansion of (CONVERT-FROM-FOREIGN-STRING CHAR-PTR 
:NULL-TERMINATED-P ...))
;   (hint: For more precise location, try *BREAK-ON-SIGNALS*.)
;   error while parsing arguments to DEFMACRO CONVERT-FROM-FOREIGN-STRING:
;     unknown keyword: :ENCODING; expected one of :NULL-TERMINATED-P, 
:LOCALE, :LENGTH
;     (DEFUN CLSQL-UFFI:CONVERT-RAW-FIELD
;            (CLSQL-UFFI::CHAR-PTR TYPE &KEY LENGTH CLSQL-UFFI::ENCODING)
;       (DECLARE (OPTIMIZE (SPEED 3) (SAFETY 0) (SPACE 0))
;                (TYPE CLSQL-UFFI::CHAR-PTR-DEF CLSQL-UFFI::CHAR-PTR))
;       (COND ((CFFI-UFFI-COMPAT:NULL-POINTER-P CLSQL-UFFI::CHAR-PTR) NIL)
;             (T
;              (CASE TYPE
;                (:DOUBLE #) 

;                (:INT #) 

;                (:INT32 #) 

;                (:UINT32 #) 

;                (:UINT #) 

;                (# #) 

;                (:BLOB #) 

;                (T #))))) 

; --> PROGN EVAL-WHEN


On 04/20/2010 11:40 AM, Kevin Rosenberg wrote:
> Changes: clsql-uffi.asd now depends on UFFI version 2.x to
> ensure a compatible version of UFFI is loaded.
> [Thanks for the idea, Robert!]
>
> Kevin
>
> _______________________________________________
> CLSQL mailing list
> [email protected]
> http://lists.b9.com/cgi-bin/mailman/listinfo/clsql
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.