- May 02, 2010
-
-
Francois-Rene Rideau authored
* have system depend on asdf. * know how to recover when signals dropped. * define parallel-load-system, parallel-compile-system. * make test executable as a shell script. * I can make clisp break mostly reliably on fare-utils if both module pure and stateful depend on base as well as interface(!) it then claims "Cycle detected".
-
- Apr 30, 2010
-
-
Francois-Rene Rideau authored
-
- Apr 29, 2010
-
-
Francois-Rene Rideau authored
instead have the new operations depend on both "internal" component-depends-on dependencies AND on "external" component-do-first dependencies, both frobbed.
-
- Apr 27, 2010
-
-
Francois-Rene Rideau authored
-
- Apr 16, 2010
-
-
Francois-Rene Rideau authored
-
- Oct 25, 2009
-
-
Francois-Rene Rideau authored
-
- Oct 02, 2009
-
-
Francois-Rene Rideau authored
-
- Sep 29, 2009
-
-
Francois-Rene Rideau authored
-
- Sep 28, 2009
-
-
Francois-Rene Rideau authored
1- Better explain how to use it. 2- Explain why we redefine classes. Sigh. 3- Use :keywords for LOOP keywords. 4- have the test auto-exit.
-
- Sep 26, 2009
-
-
Francois-Rene Rideau authored
i.e. you can (asdf:load-system :poiu) rather than manually doing (load "/path/to/poiu.lisp")
-