Tue Dec 30 01:45:38 UTC 2008 Luis Oliveira loliveira@common-lisp.net * manual: miscellaneous improvements
- use a roman font for comments in the TeX outputs. - fix some typos and missing @lispcmt{}s. - insert page breaks before each CLHS-style documentation node. This should make it much clearer to read and browse, at the expense 23 more pages in total, a ~25% increase.
M ./doc/cffi-manual.texinfo -17 +78
An updated tarball of CFFI's source can be downloaded here: http://common-lisp.net/project/cffi/tarballs/cffi-081230.tar.gz
Darcsweb URL: http://common-lisp.net/cgi-bin/darcsweb/darcsweb.cgi?r=cffi-cffi;a=summary
FFI is an optional clisp feature. Thus I propose adding it to CFFI's list of dependencies.
diff cffi.asd :author "James Bielman jamesjb@jamesjb.com" :version "0.10.3" :licence "MIT" - :depends-on (alexandria trivial-features babel) + :depends-on (alexandria trivial-features babel #+clisp ffi) :components ((:module src :serial t
This allows ASDF users to autodetect that CFFI can't load, instead of waiting for the failure at compile time.
Thanks, Daniel
On Fri, Jan 2, 2009 at 5:26 AM, Daniel Herring dherring@tentpost.com wrote:
FFI is an optional clisp feature. Thus I propose adding it to CFFI's list of dependencies.
[...]
- :depends-on (alexandria trivial-features babel #+clisp ffi)
[...]
How about a #-ffi (error "CFFI requires a version of CLISP compiled with the FFI module.") in src/cffi-clisp.lisp? Or something like that in cffi.asd. What'd be the advantage of putting that in the ASD file?
"Luís Oliveira" luismbo@gmail.com writes:
How about a #-ffi (error "CFFI requires a version of CLISP compiled with the FFI module.") in src/cffi-clisp.lisp? Or something like that in cffi.asd. What'd be the advantage of putting that in the ASD file?
Presumably you'd also want runtime warning for CFFI compiled in an image with FFI and loaded in one without.
On Fri, 2 Jan 2009, Luís Oliveira wrote:
On Fri, Jan 2, 2009 at 5:26 AM, Daniel Herring dherring@tentpost.com wrote:
FFI is an optional clisp feature. Thus I propose adding it to CFFI's list of dependencies.
[...]
- :depends-on (alexandria trivial-features babel #+clisp ffi)
[...]
How about a #-ffi (error "CFFI requires a version of CLISP compiled with the FFI module.") in src/cffi-clisp.lisp? Or something like that in cffi.asd. What'd be the advantage of putting that in the ASD file?
I'm trying to write a tool to load a collection of ASDF packages, skipping those which won't work on a given implementation/platform. With ffi in the ASD defsystem, I can query asdf:component-depends-on before loading or handle ASDF:MISSING-DEPENDENCY at load time.
An ad-hoc error requires me to know in advance not to load CFFI, but it does provide a custom error message.
- Daniel
P.S. I think its an ASDF defect that there is no mechanism for separately specifying dependencies on other packages, *features*, and arbitrary predicate functions. With optional documentation for each.
On Fri, 2009-01-02 at 00:26 -0500, Daniel Herring wrote:
FFI is an optional clisp feature. Thus I propose adding it to CFFI's list of dependencies.
diff cffi.asd :author "James Bielman jamesjb@jamesjb.com" :version "0.10.3" :licence "MIT"
- :depends-on (alexandria trivial-features babel)
- :depends-on (alexandria trivial-features babel #+clisp ffi) :components ((:module src :serial t
This allows ASDF users to autodetect that CFFI can't load, instead of waiting for the failure at compile time.
have you actually tried to do this and managed to load CFFI ? on my computer I get a "component #:FFI not found, required by #<SYSTEM "cffi" #x2060D7B6>"
On Fri, 2 Jan 2009, Stelian Ionescu wrote:
On Fri, 2009-01-02 at 00:26 -0500, Daniel Herring wrote:
FFI is an optional clisp feature. Thus I propose adding it to CFFI's list of dependencies.
diff cffi.asd :author "James Bielman jamesjb@jamesjb.com" :version "0.10.3" :licence "MIT"
- :depends-on (alexandria trivial-features babel)
- :depends-on (alexandria trivial-features babel #+clisp ffi) :components ((:module src :serial t
This allows ASDF users to autodetect that CFFI can't load, instead of waiting for the failure at compile time.
have you actually tried to do this and managed to load CFFI ? on my computer I get a "component #:FFI not found, required by #<SYSTEM "cffi" #x2060D7B6>"
No I hadn't. This was a scatterbrained idea. Sorry for the noise.
- Daniel
-
Daniel Herring -
Luis Oliveira -
Luís Oliveira -
Stelian Ionescu -
Stephen Compall