From klaus at mu.dk Thu Jun 8 09:24:28 2006 From: klaus at mu.dk (Klaus Harbo) Date: Thu, 08 Jun 2006 11:24:28 +0200 Subject: [cl-muproc-devel] New version of cl-muproc (was: Reorg of impl-dep functions) In-Reply-To: References: <6E2AC665-29E5-48F8-80D4-2EC7C317A2B6@constantly.at> <447AB9B6.3060500@mu.dk> <77F8E38D-EE86-400E-91BA-912EF17F5BF3@constantly.at> <447B6135.7080303@mu.dk> Message-ID: <4487ECCC.3050506@mu.dk> Rudi Schlatte wrote: > Hmm, muproc-compat.lisp (in your proposal below) would be essentially > documentation, and would only be loaded on otherwise unsupported Lisp > implementations. In that light, would it make sense to create > muproc-compat.txt (or porting.txt) and document the muproc-compat > interface there? Alternatively, the documentation could also be written > as comments in the :exports section of the defpackage form for the > cl-muproc.compat package. There's a new version of cl-muproc incorporating Rudi's new with a few modifcations... I decided that with implementation specific files, muproc-compat.lisp did not make much sense. I think the package definition for cl-muproc.compat defines the required implementation specific functionality adequately, and decided to add a PORTING file briefly describing the intended structure of implementation specific code instead. The new version compiles without warnings and passes the test on Lispworks. Enjoy. -Klaus. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3368 bytes Desc: S/MIME Cryptographic Signature URL: