From: Fred C. <fc...@al...> - 2010-11-21 13:18:22
|
On 11/20/10 11:42 PM, Sam Steingold wrote: > Hi, > >> * Pascal J. Bourguignon <cwo@vasbezngvzntb.pbz> [2010-11-20 04:55:13 +0100]: >>... > Because we are now using dynamic modules by default. > Use '(require "rawsock")' or whatever module you want. > Do you think the "full" module set is still necessary? > Bruno, what do you think? > >> How can I get the full link set? > > the "make distrib" still includes it. > I think I will drop it there too. >From my point of view, I would like to have a single unified make command that includes all of the external stuff required to do anything and everything that clisp can do. This includes the things like line editing and other libraries that cause failures when normal people try to do a build from scratch on a brand new system. Also, I think it would be a good idea to make sure that the same magical build command includes all of the modules so that nothing else is required, and so that - for example - we could then distribute a full up version that does everything in a single tar (or jar with some self-extraction code, or other self-extracting thing of arbitrary sort). A full-up self-test should be built in as well, so that the build is fully tested to the extent feasible at the initial build. Finally - while I am asking - it would be nice to see a way to automatically run tests on all functions used within a file, module, etc. including dependencies, so that any programmer could do, in essence, a self-test call (self-test 'file "pathname) or (self-test 'function 'functionname) or (self-test 'module modulename) or whatever and get back a T of NIL with perhaps optional explanation if not T. Just some random thoughts. FC -- -This communication is confidential to the parties I intend it to serve- Fred Cohen & Associates tel/fax: 925-454-0171 http://all.net/ 572 Leona Drive Livermore, CA 94550 Join http://groups.google.com/group/fca-announce for our mailing list |