Hi,
On Fri, Mar 28, 2008 at 5:37 AM, Chun Tian (binghe)
<[EMAIL PROTECTED]> wrote:
Though LispWorks cannot use a >=version like compile feature like
those in
Allegro, but since LW is very stable and its version grows very
slowly
(0.1/year ^_^), I think we can use #+(and lispworks-64bit (not
lispworks5.0)) to mean "LispWorks 64-bit version >= 5.1"
183c193
< #+#.(cl:if (cl:find-symbol "FOREIGN-TYPED-AREF" "FLI") '(and) '(or))
---
#+#.(cl:if (cl:find-symbol "FOREIGN-TYPED-AREF" "FLI") '(and
lispworks-64bit (not lispworks5.0)) '(or))
IIUC, this would disable this optimization for all non-64bit
platforms. It seems easier to simply state that CFFI long-longs
require LW version 5.1 or greater on 64-bit platforms. Got any
objections against that?
I ... think CFFI should support LispWorks 5.0 for long-long, because
5.0 (64-bit) do support it and not every 5.0 user can upgrade to 5.1
(new license and money is required). And (I think) LispWorks will
continue support 5.0 by release new patches in the future. For me, I'm
using both 5.0 and 5.1 right now. Without long-long support, it is
impossible to compile IOLIB on LispWorks 64-bit 5.0.
Since it's not hard to consider both versions, I (personal) hope you
can support them both, and that will be perfect.
Regards,
Chun Tian (binghe)
--
Luís Oliveira
http://student.dei.uc.pt/~lmoliv/
_______________________________________________
cffi-devel mailing list
cffi-devel@common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/cffi-devel