4:50:03jmesThanks for the info all of you, and the appropriate CLHS links :)
4:52:34jmesSorry I dropped my question and ran off for a bit. The answer illuminates some neat behaviour, thanks! Now I should go delete some redundancy in my code...
14:47:13dimHi friends! I have another pgloader related question, with SBCL 2.2.6 (available in debian sid): An unhandled error condition has been signalled: deleting unreachable code
14:47:27dimdoes that ring a bell as something new that could happen when compiling lisp code at run-time?
14:55:53dimI believe it comes from here, that's my best informed guess at the moment
14:56:25dimjust a simple call to the compile function; is the list of conditions reported there documented somewhere? what would code that ignore warnings look like?
14:59:34beachIf it is just a note, then that means that the compiler has been able to prove that some code is never going to be executed.
15:00:38dimyeah I'm okay with that, I don't know before-hand what users are going to provide as input for the command language
15:01:07dimI suppose I could somehow arrange for producing lisp code where that never happens, it kind of sounds like the job of the compiler though?
15:02:33beachIf that note is given in code written by the programmer, it indicates a defect. If it is given in some automatically generated code, perhaps not.
15:03:57BikeI didn't explain what I meant correctly