11:52:20beachWhat aspect of those? Time of hoisting? Implementation-specific compiler?
11:54:27heisigbeach: Time of hoisting. I have already started investigating how ECL, SBCL, ABCL, Clisp and CCL handle the issue and how they produce their .fasl files.
11:56:20heisigQuestion: You mentioned it is not possible to perform minimal compilation during AST generation to get the AST environment-free, but why is that so?
11:56:45jackdanielheisig: keep in mind ECL have two different kinds of fasl which behave differently: FAS (which is ELF shared object) and FASC (which is bytecodes vector)
11:57:50beachheisig: I said that? That doesn't sound familiar? Perhaps I said "implementation independent" rather than "environment free"?
11:59:10Bikei'm not sure what "perform minimal compilation during AST generation" means. ast generation does do minimal compilation (and more)
12:00:09heisigOk, then I misunderstood that. Thank you for the clarification.
12:02:18heisigjackdaniel: Oh, interesting. I only found the ELF fasls so far. I need to check the code again.
12:04:16jackdanielheisig: you activate bytecodes compiler with (ext:install-bytecodes-compiler)
12:04:38jackdanielbytecmp is default on windows (because c compiler is not present at runtime there)
12:06:11heisigjackdaniel: Thank you! What a luxury to have the main ECL developer around :)
12:07:02jackdanielas of ELF fasls, you may be interested in investigating intermediate files - you may pass arguments to compile-file so they are not removed
12:07:51jackdaniel(keywords :c-file :h-file and :data-file afair)
12:10:28jackdanielals this may be interesting to you (but not so much as having intermediate files): https://common-lisp.net/project/ecl/static/ecldoc/Extensions.html#Compiling-with-ECL