21:23:28froggeyyou need to use (sys.int::function-code-size function) and (sys.int::function-code-byte function index) to read a compiled function's machine code
21:25:09houselfroggey: what are the semantics of expunge-directory intended to be?
21:25:27ebrascaMaybe it is better to focus on assambler alone and 0 dissambler.
21:27:07froggeyit should actually remove any deleted files in the given directory, like emptying the recycle bin. I haven't thought about it beyond that
21:27:42houseland there's currently no remove-directory, right?
21:28:29houselI'm working on adapting quicklisp, and that's one of the operations it wants to be able to do
21:30:14froggeyI think delete-file with a directory argument should cover that. the hyperspec isn't very clear here
21:32:31houselquicklisp uses delete-file as its default implementation, but quite a few platforms have another function for directories
21:35:14housel(I also have a fix for defpackage that I'll submit a PR for this evening)
21:37:14froggeyebrasca: you can bind sys.c::*trace-asm* to T or :FULL and the compiler will print what it's passing to the assembler. I used that and objdump/other disassemblers while developing most of the system
21:37:51froggeythe native disassembler is a very recent addition, though it's very nice to have and I use it a lot now