- Feb 02, 2010
-
-
Pascal Costanza authored
Ignore-this: bdb877b84b8b53d0da7c781833813219 darcs-hash:6eaf63cedfed2bc4c5bc15878e625fb5176a7b20
-
- Nov 21, 2009
-
-
Pascal Costanza authored
Major reorganization of the code, plus support for generic function invocation protocols in Allegro Common Lisp. Ignore-this: 9be21704dcdc2ab8e47f596e5a82ff3b A major reorganization of the code became necessary, because the old structure became harder than necessary to maintain. I have now moved code that is similar across many Common Lisp implementations into a shared source code file, and leave only small parts to implementation-dependent source code files. The setup of packages is combined into one file, and all relevant symbols are now exported from the packages, including symbols that may not have any definitions in some Common Lisp implementations. To further simplify things, I have moved source code from subfolders into the main folder, to avoid hierarchy creep. Finally, Allegro Common Lisp now also supports the full generic function invocation protocols. darcs-hash:4b756a79272aa1381988469961dd04652b9f712b
-
- Nov 17, 2009
-
-
Pascal Costanza authored
Ignore-this: 8505094d361aee4763045939771f8cfa Originally, when I started Closer to MOP, I expected implementations that stem from the same original implementations to have similar issues with regard to CLOS MOP compatibility. So specifically, I packaged the code for CMUCL and SBCL into one folder, and that for MCL, OpenMCL and Clozure Common Lisp into one folder. It turned out that the incompatibilites are not at all similar, and that this created more problems than it solved. So I now decided to keep implementations strictly separated, to make my life easier in the future. darcs-hash:b18e457aea79fad11fed31cb4d2e94af211cc4ef
-