The attached patch adds a :type attribute to foreign libraries(:system or :wrapper), per-library search paths(needed for cffi-grovel wrappers) and a function list-foreign-libraries. It also adds the readers foreign-library-type, foreign-library-search-path and foreign-library-loaded-p. Any objections against merging this ?
The attached patch adds a :type attribute to foreign libraries(:system or :wrapper), per-library search paths(needed for cffi-grovel wrappers) and a function list-foreign-libraries. It also adds the readers foreign-library-type, foreign-library-search-path and foreign-library-loaded-p. Any objections against merging this ?
I haven't been following your work closely. What was the distinction between :system and :wrapper libraries?
Thanks, Daniel
On Thu, 2009-07-09 at 10:35 -0400, dherring@tentpost.com wrote:
The attached patch adds a :type attribute to foreign libraries(:system or :wrapper), per-library search paths(needed for cffi-grovel wrappers) and a function list-foreign-libraries. It also adds the readers foreign-library-type, foreign-library-search-path and foreign-library-loaded-p. Any objections against merging this ?
I haven't been following your work closely. What was the distinction between :system and :wrapper libraries?
:wrapper libraries are those auto-generated by cffi-grovel, while :system libraries are those installed on the machine (/lib, /usr/lib, etc...)
On Thu, Jul 9, 2009 at 5:04 PM, Attila Lendvaiattila.lendvai@gmail.com wrote:
:wrapper libraries are those auto-generated by cffi-grovel,
could their name contain the word "grovel" in any way? my english is lacking for this, but it would be much more intuitive than :wrapper...
Another idea would be that cffi-grovel subclasses cffi:foreign-library and do something with that. Not sure if it's overkill, though.
On Thu, 2009-07-09 at 17:27 +0100, Luís Oliveira wrote:
On Thu, Jul 9, 2009 at 5:04 PM, Attila Lendvaiattila.lendvai@gmail.com wrote:
:wrapper libraries are those auto-generated by cffi-grovel,
could their name contain the word "grovel" in any way? my english is lacking for this, but it would be much more intuitive than :wrapper...
Another idea would be that cffi-grovel subclasses cffi:foreign-library and do something with that. Not sure if it's overkill, though.
I tried that too, but ATM it's useless: I got to the point where I had the classes foreign-library, system-library and wrapper-library but only foreign-library needed initialization(after refactoring, the other two classes had empty initialize-instance methods). The difference between :system and :wrapper libraries is only intentional, not factual.
On Thu, 2009-07-09 at 18:04 +0200, Attila Lendvai wrote:
:wrapper libraries are those auto-generated by cffi-grovel,
could their name contain the word "grovel" in any way? my english is lacking for this, but it would be much more intuitive than :wrapper...
ok, I made that :grovel-wrapper
-
Attila Lendvai -
dherring＠tentpost.com -
Luís Oliveira -
Stelian Ionescu