freenode/lisp - IRC Chatlog
Search
12:12:09
drmeister
jackdaniel: ECL has this thing ECL_USE_MPROTECT that uses mprotect to trap access to the environment to indicate that there is a pending signal. I don't understand why that is faster than the alternative of calling ecl_check_pending_interrupts(env) in https://gitlab.com/embeddable-common-lisp/ecl/blob/develop/src/h/external.h#L1865
12:13:03
drmeister
I don't know if you have dug into this part of ECL - but do you have any insight as to why using mprotect is faster than the alternative?
12:16:40
flip214
drmeister: probably because checking a flag in tight loops costs performance in each iteration, while the "memory protection fault" comes mostly free with the next access
12:26:51
jackdaniel
didi: ASDF manual is updated frequently and ASDF's API change, you probably have version bundled with your implementation
12:28:48
jackdaniel
oh, then you'll probably be out of luck with getting help here (people rarely use lisp-controller from my observation)
12:29:36
didi
jackdaniel: I don't think lisp-controller is used much nowadays in Debian, but I might be wrong.
12:30:08
iago
that's something I was asking on clnoobs. What is better use the libraries provided by your package manager or to set up your own environment ?
12:30:52
jackdaniel
for development its better to use quicklisp (and that's what most people do) – deployment is another story
12:31:24
flip214
Sorry. I'd *like* to use debian packages (because they'd be kept up to date "automatically"!), but unfortunately most are too old. So I use Quicklisp too.
12:32:01
flip214
jackdaniel: QL can use older package sets as well, so some fixed-version deployment is easy as well