freenode/#lisp - IRC Chatlog
Search
17:21:01
Xach
and http://report.quicklisp.org/2017-07-17/failure-report/mcclim.html#mcclim-raster-image
17:25:34
jackdaniel
I'll have to add a test for loading all systems separately for mcclim (and simplify the dependency tree), because these errors are quite regular
17:51:08
phoe
"This generic function implements the behavior of the slot-value function. It is called by slot-value with the class of object as its first argument and the pertinent effective slot definition metaobject as its third argument."
17:52:02
phoe
by the broad definition, an accessor is just a function that retrieves or stores data.
17:52:19
Bike
beach: we have, but i'm observing different behavior from an accessor and from s-v-u-c, so i'm adrift
17:53:01
Bike
no, no, i mean i tried some stuff and calling setf slot-value directly does things that setf accessor does not
17:54:26
beach
That is one thing that should not be possible, unless those other things are defined by the implementation only and not generally available to the application programmer.
17:55:54
Bike
cool. just means there's some obscure bug in sbcl with method redefinition, or something
17:55:57
beach
If everything is MOP defined: The class metaclass, the class of the generic function, the slot metaobject, etc., then the accessor may avoid calling slot-value etc.
17:57:24
nosefouratyou
hey I am trying to fix up logv at the moment and I am getting stuck on this issue: https://github.com/nallen05/logv/blob/master/logv.lisp#L31 https://gist.github.com/nosefouratyou/24d444ebe831612192f75f1c3e67f33a
17:57:52
beach
Bike: I am not talking about custom classes and custom methods. I am talking about custom metaclasses and custom method classes.
17:58:43
beach
If all you have is custom methods on custom classed, but the metaclasses are standard, then the slot accessor may avoid calling slot-value-using-class if it is the only applicable method.
18:00:39
beach
That's fine, and in cases like that, the slot accessor may not be able to avoid calling slot-value-using-class.
18:05:16
nosefouratyou
but I had it running today; I removed in and downloaded it again and now I can't figure out what I did to fix it
18:08:25
Thetabit
I'm sure this is dumb, but I am going thru the Slime manual looking at the commands for debugging, but I don't know how to start the debugger without hitting an error first. How do I get into the debugger and then step into the expressions? Am I approaching debugging with the wrong mindset, eg treating emacs and slime like an IDE where I can set breakpoints?
18:08:28
Bike
i'm pretty sure. from the package definition that's cl:defsetf, and defsetf has a defsetf lambda list, and those don't have that list thing.
18:08:47
Bike
Thetabit: it is a bit unusual to do it like that. but you can insert calls to (break) in your code
18:08:48
nosefouratyou
Thetabit: you can use (break) anywhere in your program to trigger the debugger
18:09:29
kencausey
nosefouratyou: Actually, I don't see logv listed in quicklisp currently, I may have misspoken. Is your quicklisp out of date?
18:10:24
Bike
nosefouratyou: try making it optional. (key &optional (log-env-name *default-log-env*))
18:10:29
Xach
https://sites.google.com/site/sabraonthehill/comparison-of-lisp-logging-libraries has some hints
18:10:39
Xach
>> I do want to mention that I have left out at least two. First, logv, which I could not get to compile.
18:11:50
Bike
logv doesn't show up in system-apropos. maybe you have it otherwise accessible from asdf, like from quicklisp local-projects.
18:54:07
phoe
But it looks like I can compress and decompress arbitrary Lisp uint8 vectors, which is good.
18:55:38
phoe
The best part - I needed to build the .so library for Linux myself because the original LZMA makefile from Igor Pavlov only builds binary executables.
19:30:36
phoe
tetero: working out, as in? It works for me so far for trivial arrays, I have not tested it much yet, it's freshly out of the oven
19:34:39
phoe
the header files for LZMA got parsed automatically and I got all the required C functions, types and sizes automagically
19:35:49
phoe
but I spent whole two hours debugging an issue that size_t was eight bytes where I only allocated four - and boom, heisenbugs, image corruptions, drops to LDB and such fun stuff.
19:39:28
phoe
because I thought that I should allocate four there as size_t wasn't called size_t in the original code but had some quirky typedef that made me assume it's four bytes.
20:29:39
otwieracz
Is this possible to kill a thread (or better, send an interrupt) from slime-list-threads?
20:31:44
Bike
https://trac.common-lisp.net/bordeaux-threads/wiki/ApiDocumentation#interrupt-threadthreadfunction
20:41:02
Baggers
otwieracz: swank has both interrupt-thread & kill-thread but I cant recall on the slime side
20:42:15
Baggers
otwieracz: I guess you would (slime-eval `(swank:kill-thread (some-cl-func-to-get-thread))) but I'm not 100% on that
20:50:55
Baggers
otwieracz: does bt:interrupt-thread work? also is it your thread and do you have an idea of why it might be blocking? Where a blocking call is needed it could be worth looking for a similar function with a timeout
21:15:22
Bike
regl: usually i work with subsystems... i think there are directions in the readme now, though
21:17:23
regl
debugger invoked on a UIOP/LISP-BUILD:COMPILE-FILE-ERROR in thread #<THREAD "main thread" RUNNING {10031A63F3}>: COMPILE-FILE-ERROR while compiling #<CL-SOURCE-FILE "cleavir-environment" "compile-time">