"Hoehle, Joerg-Cyril" <[EMAIL PROTECTED]> writes: > BTW, do you have an idea how I can put your "try it out" %mem-set > patch into darcs without getting upset by merge conflicts the day > you'll push it onto the darcs repository?
Either try it out in a separate tree, or apply the patch in your tree and revert it afterwards with 'darcs revert'. > Here's another suggestion: I think the uffi-compat needs an ASDF > definition file named uffi.asd, or at least a defsystem uffi in some > file. So users can at least (load "cffi-as-uffi.asd") to make ASDF > believe that uffi is there. Reason: packages using (depending on) > UFFI will otherwise load the real uffi or error out when not > available. Or how did you manage to load some UFFI-using package with > CFFI instead? I just edit the package's .asd file and make it :depend-on :cffi-uffi-compat instead of :uffi or, for instance, #-clisp :uffi #+clisp :cffi-uffi-compat (this is what's done in CL-GD). I suppose a dummy uffi.asd file (that would depend on cffi-uffi-compat) could be useful. Perhaps we should create a contrib/ directory and place such a .asd file there? Note to self: these two approches should be mentioned in the user manual. -- Luís Oliveira luismbo (@) gmail (.) com Equipa Portuguesa do Translation Project http://www.iro.umontreal.ca/translation/registry.cgi?team=pt _______________________________________________ cffi-devel mailing list cffi-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/cffi-devel
