[clisp-list] LOOP extension (was: sql libraries)

[<don...@is...>]

Hoehle, Joerg-Cyril writes:
 > Some implementation of the LOOP macro provide for user defined
 > iteration clauses.  E.g. the very old MIT-LOOP code has IIRC
 > DEFINE/ADD(?)-LOOP-PATH to define this.  The user's definition
 > looks much like a setf-expander and returns IIRC seven values:
 > snippets of code that the LOOP macro will insert in various places
 > of its extension.
 > 
 > CLSQL uses this extension where available (e.g. cmucl, Lispworks AFAIK).

To me the obvious solution is that CLSQL should come with its own
copy of the loop macro for use only in its own package(s).  
This is what ap5 does.
I don't think that one piece of software ought to change the way the 
loop macro (or other shared functionality) works in others.

I never understood why clisp (or any other common lisp implementation)
reimplemented loop.