<p><a href="https://screwlisp.small-web.org/conditions/partial-gopher-client/" rel="nofollow" class="ellipsis" title="screwlisp.small-web.org/conditions/partial-gopher-client/"><span class="invisible">https://</span><span class="ellipsis">screwlisp.small-web.org/condit</span><span class="invisible">ions/partial-gopher-client/</span></a></p><p><a href="/tags/commonlisp/" rel="tag">#commonLisp</a> <a href="/tags/conditionhandling/" rel="tag">#conditionHandling</a> implemented as a <a href="/tags/gopher/" rel="tag">#gopher</a> protocol using <a href="/tags/emacs/" rel="tag">#emacs</a> <a href="/tags/slime/" rel="tag">#slime</a> as the client.</p><p>This is even better than it sounds.</p><p>The condition handling system (nonfatal generalization of exception handling using lisp's local restarts/continuations) is unexplored and seen as opaque.</p><p>Using this tiny but esoteric example the available non-lexical computed restarts of an interactive condition are simply /browsable/.</p><p><a href="/tags/programming/" rel="tag">#programming</a> <a href="/tags/softwareengineering/" rel="tag">#softwareEngineering</a></p><p><span class="h-card"><a href="https://climatejustice.social/@kentpitman" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>kentpitman</span></a></span></p>
Edited 37d ago
