<beach>
"the &environment parameter is bound along with &whole before any other variables in the lambda list, regardless of where &environment appears in the lambda list."
JuanDaugherty has quit [Read error: Connection reset by peer]
rbcarleton has joined #commonlisp
Oddity has quit [Ping timeout: 276 seconds]
rbcarleton has quit [Client Quit]
makomo has joined #commonlisp
admich1 has quit [Ping timeout: 252 seconds]
decweb has joined #commonlisp
admich1 has joined #commonlisp
stanrifkin_ has left #commonlisp [Leaving]
donlcn has quit [Remote host closed the connection]
donlcn has joined #commonlisp
chomwitt has joined #commonlisp
admich1 has quit [Read error: Connection reset by peer]
admich1 has joined #commonlisp
admich1 has quit [Ping timeout: 252 seconds]
prokhor-zhakarov has quit [Remote host closed the connection]
rgherdt has quit [Quit: ERC 5.6.0.30.1 (IRC client for GNU Emacs 30.1)]
prokhor-zhakarov has joined #commonlisp
jonatack has joined #commonlisp
rbcarleton has quit [Quit: rbcarleton]
admich1 has quit [Ping timeout: 276 seconds]
rgherdt has joined #commonlisp
admich1 has joined #commonlisp
Everything has joined #commonlisp
admich1 has quit [Read error: Connection reset by peer]
admich1 has joined #commonlisp
admich1 has quit [Read error: Connection reset by peer]
admich1 has joined #commonlisp
rbcarleton has joined #commonlisp
rbcarleton has quit [Client Quit]
ciuhh has joined #commonlisp
yitzi has quit [Ping timeout: 268 seconds]
yitzi has joined #commonlisp
yitzi has quit [Client Quit]
random-jellyfish has joined #commonlisp
random-jellyfish has quit [Changing host]
random-jellyfish has joined #commonlisp
yitzi has joined #commonlisp
zwr has quit [Read error: Connection reset by peer]
<random-jellyfish>
how do I get the file name and line number of a warning? at least the file name, line number optional
zwr has joined #commonlisp
ciuhh has quit [Remote host closed the connection]
gnoo has quit [Ping timeout: 245 seconds]
gnoo has joined #commonlisp
donlcn has quit [Ping timeout: 252 seconds]
<beach>
random-jellyfish: Isn't that obvious from the REPL buffer?
yitzi has quit [Ping timeout: 248 seconds]
<random-jellyfish>
Unfortunately not so obvious, it just gives me the path to a .fasl file from which I guess I can figure out the source file name. The problem is that the warning comes from inside a file that is loaded by the respective source file.
<beach>
Hmm, I see.
<random-jellyfish>
I mean I can find it eventually, but it's a lot of work and it's very distracting...if the errors/warnings are deeper it gets even messier
<random-jellyfish>
I think this is a major drawback for common lisp, we should be able to find the exact source location of errors and warnings...
Oladon has joined #commonlisp
<beach>
It is not a drawback of Common Lisp at all. It is a problem with the implementation.
<beach>
But I understand your frustration.
<random-jellyfish>
I use sbcl
<random-jellyfish>
Are commercial implementations addressing this issues? I haven't tried any yet
<beach>
Me neither, so I don't know.
<beach>
Even if they don't, that's still not a problem with the language.
yitzi has joined #commonlisp
<Shinmera>
conditions don't have a "file" at all. The stack frame in which it is signalled may have a recorded source position.
<beach>
Good point. Thanks for the clarification.
rbcarleton has joined #commonlisp
<Shinmera>
So first you need to access the stack frame, which you can only do if you are on top of the stack (via handler-bind). Then you can use implementation internal functions to try and access that information and hope it is provided. The library Dissect may help with that.
<Shinmera>
In Slime/Sly's debugger you can typically just hit V on the frame you care about to jump to the source location, if it is recorded.
<beach>
But the implementation could have been more helpful by including source information in the condition.
<random-jellyfish>
Shinmera, I'm loading a system like this: (sb-introspect:who-calls 'system-lisp:int-get-slice) and I get some warnings, is it possible to stop in the stack frame on a warning to use the V-key solution?
<random-jellyfish>
sorry wrong form
<random-jellyfish>
(asdf:load-system :system-lisp/tests :force t :verbose t)
<random-jellyfish>
this is how I load the system
shka has joined #commonlisp
<Shinmera>
ASDF obscures these errors, so I'm afraid not. Blame ASDF for that one.
<Shinmera>
you can try to use *break-on-signals* to force a debugger
<Shinmera>
typically however SBCL will tell you the file in which the warning occurred and the form that produced it on the REPL
Oddity has joined #commonlisp
<random-jellyfish>
using *break-on-signals* does bring up the stack frame on warnings but I can't find any item in the stack that can get me to the source code with the V key
treflip has joined #commonlisp
JuanDaugherty has joined #commonlisp
lucasb has joined #commonlisp
treflip` has joined #commonlisp
treflip has quit [Ping timeout: 244 seconds]
treflip` has quit [Read error: Connection reset by peer]
treflip` has joined #commonlisp
donlcn has joined #commonlisp
<beach>
random-jellyfish: Are you using a DEBUG quality 3? The default is lower.
<beach>
Not that I understand why it is lower by default, but hey.
iNomad has joined #commonlisp
random-jellyfish has quit [Ping timeout: 248 seconds]
random-jellyfish has joined #commonlisp
random-jellyfish has joined #commonlisp
random-jellyfish has quit [Changing host]
<random-jellyfish>
beach, I do a declaim before I load the system with asdf