freenode/#sbcl - IRC Chatlog
Search
14:01:56
Krystof
I hope that we will gather lightning talk materials and so on and post them up on the sbcl20 page (I guess we call it a "microsite" these days) afterwards
15:11:05
fe[nl]ix
Krystof: https://github.com/sionescu/sbcl/commit/a8b770d0f61a7d1d243600122db667cdd58cf9dc
15:18:23
flip214
Shinmera: I was in the program chair the last few years, but I'm not listed right now.
19:44:27
easye
flip214: The ELS2020 PC is not fixed. Definitely reach out to Ioanna as someone interested in reviewing compiler papers, and she will gladly accept help.
19:51:26
easye
Ah, yes, HP-UX on the 64bit cores descending from "Itanium". Ok, who actually knows someone who runs sbcl on HP-UX in 2019?
22:33:38
lottaquestions_
Hi all, I have a question: I am stepping through some code in which the :after function of mkinstance is run of a class. However I noticed, that the actual variable names in the :after function are not available in SLDB. Instead I see variables with the name root defaulting-temp
22:34:07
lottaquestions_
A follow up question would be, how would I run expressions of interest in the :after function in SLDB, since evaluate (e) does not have access to the variable names as they appear in the original code
23:18:02
lottaquestions_
does that mean that all functions taking keyword parameters change the variable names of the keyword parameters passed to them?
23:22:24
lottaquestions_
eg like what precipitated my original question was I was stepping through code in slime
23:23:17
lottaquestions_
but most cases, if within a function, I would naturally want to evaluate some of the subforms of the main form
23:24:00
lottaquestions_
but since how the internals of SBCL see the code is different from how I see it,
23:24:17
lottaquestions_
I am stuck being unable to do the evaluations of the forms that I want to do
23:40:24
stassats
unlike C, you don't have to recompile the whole thing and restart to insert a print or a break
23:44:42
lottaquestions_
Yeah, I've heard of trace. I am still in the discovery phase of discovering the limits of sbcl and slime
23:45:20
lottaquestions_
there have been cases where I recompiled and loaded, and sbcl ignored newly added break forms
23:47:49
lottaquestions_
what I have been doing has been C-c C-k for compile and load the current buffer's file
23:51:11
lottaquestions_
To call the new code, I was restarting the frame above the frame that contains the new code
23:52:09
lottaquestions_
unless of course there is something different I should be doing to run the new code
23:53:20
stassats
and restarting frames doesn't always get the arguments right, so be mindful of that
23:54:09
stassats
compiling new code doesn't change the actual code, just the name association to that code
23:55:51
lottaquestions_
basically all I have had as pointers on how to do this is a video by a one Marco Baringer, a blog by someone with the handle malisper and a video of some other guy debugging a web server (hunchentoot maybe? not sure)
23:56:50
lottaquestions_
I wouldn't mind pointers on the subtleties of SBCL+slime to allow me to use it effectively
23:58:07
lottaquestions_
oh...<compiling new code doesn't change the actual code, just the name association to that code>
23:58:50
lottaquestions_
how do I change the actual code ? I do not mind going and reading up if there is documentation somewhere that actually explains this
1:04:59
|3b|
lottaquestions_: if you didn't try it already, higher DEBUG (with local declarations, restrict-compiler-policy, or C-u C-c C-k, C-u C-c C-c etc in slime) might give you better debugging