Hi Alexis, "Alexis Gallagher" <[EMAIL PROTECTED]> writes:
> 2) testing and tweaking for compatibility with other CL implementations. > SBCL and CMUCL are presenting problems which are mysterious to us, but > probably transparent to someone familiar with CFFI. We're stuck, but we > think it's a simple issue (a foreign string pointer is being converted > to a CL string prematurely, but we can't figure out why). I just made a quick test with SBCL 0.9.12 on x86-64 and had to change one line in pygetarg from (string (cffi:foreign-string-to-lisp (cffi:mem-ref variable :string))) to (string (cffi:mem-ref variable :string)) Someone else posted that everything worked fine for him with a very similar configuration, so I *guess*, that it might be a change between different CFFI versions. I ASDF-INSTALLed it a few weeks ago and it is version 0.9.1. Maybe cvs CFFI is different in this regard? Regards, Marco _______________________________________________ Gardeners mailing list [email protected] http://www.lispniks.com/mailman/listinfo/gardeners
