Andreas Davour <[EMAIL PROTECTED]> writes: > Very often these packages depend on quite a few other lisp systems, > which in turn depend on another bunch. I think ASDF-INSTALL have put us > in the situation that it isn't any longer unusual for a simple task be > "solved" by a enormous blob of interdependent software.
I wouldn't call code reuse the problem. I would say that what is needed is a better method to distribute, install and manage Lisp packages. The situation totally blows in win32 with the sole exception of Edi's Lisp Starter Pack (i) > What has this to do with application-builder? Not anything directly, but > the odd dependency mentioned above reminds me how much I detest this > kind of solutions for software, and I'd like to plead to you all to not > build software that way. Ask yourself if it really is the best way. > Sometimes it can be worth it to reinvent a small wheel instead of > "re-use" barn full of utility wheels. That's fine and all, but we have two problems: (1) resources, and (2) speed. #1 - Resources: To replace the rotozoom function in sdl_gfx we need the equivalent rotozoom function in Lisp. This functionality is not going to write itself. #2 - Speed: This kind of function is always going to be 10x faster in C than the equivalent pure Lisp version. (i) Light goes off in head... extend Edi's Starter Pack to install ASDF packages from the Cliki. - Luke _______________________________________________ application-builder mailing list application-builder@lispniks.com http://www.lispniks.com/mailman/listinfo/application-builder
