Re: CLSQL version 5.1.0 released
Kevin Raison <[email protected]>
| Newsgroups | gmane.lisp.clsql.general |
|---|---|
| Organization | Chatsubo.net |
| Message-ID | <[email protected]> |
So UFFI has this function with the proper keyword? If so, how do I get clsql to use UFFI's function and not CFFI's? It seems that having both packages as dependencies can cause some strange behavior; does anyone know a good way to avoid this kind of clash? I tried removing CFFI entirely from my asdf:*central-registry*, but clsql fails to compile without it. Thanks for the help. Kevin Raison On 4/21/10 7:54 AM, Kevin Rosenberg wrote: > On Apr 20, 2010, at 10:43 PM, Kevin Raison wrote: >> 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. > > Foreign string encoding is a recent addition to UFFI so that CLSQL can > use foreign encodings. I don't know if the authors of CFFI-UFFI-COMPAT > will add encoding to their UFFI emulation library. > > Kevin >