8:59:46susamBy the way, I still keep CLISP around because (1) nostalgia (2) testing out if some implementation-dependent behaviour behaves differently with CLISP. That is, SBCL as the primary implementation and CLISP to test out my programs to weed out any bad habits of writing implementation-dependent code.
9:31:17kakuhenI like to test on CCL just to weed out sbcl-specific code
9:31:43kakuheni became really angry when doing this for a certain cl project because a bunch of really really simple functions that reinvented already-existing functions in the CL spec were using sbcl extensions
9:33:25kakuhenbut after patching out that mess... i am now just angry at one thing: every CL implementation seems to have its own posix interface and export symbols for errors and signals, but neither uiop nor osicat-posix have decided to have wrappers for this