freenode/#lisp - IRC Chatlog
Search
0:59:46
Bike
::notify phoe why does pitman's handler-case impl (and by extension yours) get out of the handler functions with a tagbody, instead of just immediately doing the return-from?
5:35:39
markasoftware
am I allowed to modify a variable during (loop) iteration, eg, (loop for blah on my-list do (setf blah something))
5:39:43
White_Flame
the loop stepping & termination conditions simply work on the value that's there, no matter how it got there
5:42:14
White_Flame
for loop for blah IN my-list, though, I don't think the cons stepping variable is exposed, but for for-ON whatever's in BLAH will have its cdr as the next iteration
7:15:42
phoe
::notify Bike What do you mean? You cannot do RETURN-FROM in this case; you need to jump from the respective handler function to the respective handler case, and from the handler case you can perform a RETURN-FROM.
7:16:15
Colleen
phoe: Bike said 6 hours, 16 minutes ago: why does pitman's handler-case impl (and by extension yours) get out of the handler functions with a tagbody, instead of just immediately doing the return-from?
7:16:20
Colleen
Unknown command. Possible matches: 8, grant, time, tell, set, say, mop, get, have a, block,
7:46:15
phoe
::notify Bike This is required because you first need to transfer control out of whatever place you are executing, and only then execute the handler case. If you want to first execute the handler stuff and only then leave control, see test-1 and test-2 in https://github.com/phoe/tclcs-code/blob/master/98-handler-bind-case/clcs-98-handler-bind-case.lisp