freenode/#lisp - IRC Chatlog
Search
23:28:43
comborico1611
I'm trying to find the connection to the word apropos, and its namesake function. Any ideas?
1:35:58
karlosz
well, it looks like this particular issue was fixed in the latest commit to quicklisp
1:50:09
clintm
Is clisp the one that gets updated by loading new code into a previous revs image? I remember reading about a CL that did that as opposed to building a new image like sbcl.
1:51:29
Zhivago
I wouldn't recommend it these days. Image building is pretty much something that was useful until dynamic linkage became available.
1:52:12
theemacsshibe[m]
image making is nice tbh, i use it to distribute lisp programs to non-lisp users
1:53:06
Plazma
while not the same, smalltalk also uses images (that are pretty easy to build/strip down) which is a cool concept I think still, even if it's a bit dated
1:54:12
theemacsshibe[m]
it's possible to mess (especially with -g) with but not as good as having sources
2:09:39
karlosz
its whole existence was ttying to move away from the CMUCL style build to the reproducible build we all know and love
3:04:14
loke
Bike: Oh it does? I tried it a few moenths ago, and back then Drmeister said it was planned but not working yet.
4:24:13
aeth
Does anyone else use a macro as the way to access things to avoid potentially dozens of exports in a package? What I've been doing is a with-foo-accessors that places the accessor symbols in the package specified at the definition of that macro and also can add a prefix (for the case of structs with conc-name not set to nil).
4:25:03
aeth
I find that this greatly simplifies things because then I only need to export the with-foo-accessors macro and/or a macro that indirectly uses that macro.
4:26:59
aeth
e.g. (with-foo-accessors ((foo foo)) foobar ...) would macroexpand to (with-accessors ((foo the-package-containing-foobar::foobar-foo)) foobar ...) in the most complicated case (where it's a struct with prefixed accessors)
4:44:08
aeth
My macro, in case anyone's curious: https://gitlab.com/zombie-raptor/zombie-raptor/blob/ec47910d88254d0c6a0e8c0a33aa33c7d4037513/util/util.lisp#L247-260
4:44:36
aeth
destructuring-lambda is just a lambda that does a destructuring bind on its one argument. It's surprisingly common. In fact, I just now noticed the pattern in define-accessor-macro
5:09:42
aeth
loke: Otherwise the macro will produce something whose API is (zombie-raptor/util/util::foo)
5:33:15
aeth
loke: I use #.(symbol-name ...) pretty much everywhere instead of hardcoding the symbol as a string of upper case characters
5:38:49
aeth
I know it's essentially pointless, but at least to me it feels better to not hardcode the assumption about the reader that will almost certainly be valid. Perhaps this could be turned into something more concise?
5:42:31
aeth
But... I suppose I should be using &environment env instead of assuming intern without that argument would work correctly
8:00:01
scymtym
shka: glad you like it. but i have to learn more CLIM or get somebody to help out to make it less horrible to use