xkapastel has quit [Quit: Connection closed for inactivity]
orivej has quit [Ping timeout: 252 seconds]
ubLIX has quit [Quit: ubLIX]
orivej has joined #picolisp
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #picolisp
orivej has quit [Ping timeout: 245 seconds]
jibanes has quit [Ping timeout: 240 seconds]
jibanes has joined #picolisp
orivej has joined #picolisp
_whitelogger has joined #picolisp
jibanes has quit [Ping timeout: 246 seconds]
jibanes has joined #picolisp
xkapastel has joined #picolisp
razzy` has left #picolisp [#picolisp]
razzy has joined #picolisp
<razzy>
when i do 1. hit C-c C-c, 2. reload function-i-am-debbugging with added !, 3. continue to run picolisp,... debugger do not stop at added ! often even break. i think it is no way around it. do i need to (quit), reload, run again? \n Could i somehow single step without (d)? more like sequence "(unbug 'current-higher-function) (d) /n"?
<tankf33der>
/join #solaris
<Regenaxer>
Hi razzy! The loaded function will not run before the currently executed expression is exited
<Regenaxer>
Think about what happens: The reader creates a new s-expr during 'load', and stores it in the function's symbol
<Regenaxer>
The currently stopped execution is in another s-expr
<Regenaxer>
To do what you want you must destructively modify the current expr
<Regenaxer>
(d) does this in principle
<Regenaxer>
it calls 'dbg' which destructively modifies the expression
<Regenaxer>
'load' is not destructive
<razzy>
Regenaxer: I agree, that is why i put wording as i did.is there good workflow? is somewhere in picolisp lastly called function?
<Regenaxer>
Yes, the stack backtrace
<Regenaxer>
See 'trail'
<razzy>
hmm hmm, thx
andyjpb has joined #picolisp
DKordic has joined #picolisp
ubLIX has joined #picolisp
groovy2shoes has quit [Quit: moritura te salutat]
mtsd has joined #picolisp
michelp has quit [Ping timeout: 252 seconds]
michelp has joined #picolisp
pchrist has quit [Ping timeout: 252 seconds]
razzy has quit [Read error: Connection reset by peer]