freenode/#lisp - IRC Chatlog
Search
21:41:48
phoe
flip214: thanks for the review! The typesetting isn't final at all, I'll still be moving things around
21:42:08
phoe
I mostly wanted a review of the content; I didn't specify that clearly, so sorry about that
0:03:22
emaczen
Is CFFI just a portability library using the FFI of whatever CL implementation is being used?
0:04:15
luis
CFFI-SYS is a portability layer. And then CFFI implements a bunch of features on top of that.
0:07:41
void_pointer
emaczen: if you want to see how cffi-sys uses the features of whatever implementation it is on (out of a particular list), take a look at the different implementation specific files in https://github.com/cffi/cffi/tree/master/src
0:08:45
void_pointer
emaczen: for example, if you look in the SBCL one (https://github.com/cffi/cffi/blob/master/src/cffi-sbcl.lisp), you will see heavy use of the sb-sys package that is builtin to SBCL
0:09:49
void_pointer
emaczen: there are probably some uses of it there too. Just, sb-sys was what stood out to me just a minute ago.
0:11:46
void_pointer
most of the time one doesn't need to access it directly, and just use cffi which uses it in the background
1:32:24
emaczen
How do cffi:defcvar cffi:defcfun and cffi:defcstruct work and how does C expose variables, functions and structs so that we can interface?
2:20:41
p_l
emaczen: usually whatever the operating environment has for dynamic symbol resolution, which gives back pointer, which is wrapper appropriately for the Lisp code
4:09:02
minion
specbot: #11911: You wrote the same thing twice here. The cardinal rule of programming is that you never ever write the same thing twice.
4:13:03
minion
#11918: Well, then get one that *does* do auto-indent. You can't do good work with bad tools.