On Mon, 2008-11-03 at 23:44 +0100, Lars Rune Nøstdal wrote:
> On Mon, 2008-11-03 at 14:18 -0800, budden wrote:
> > > (defpackage my-lisp-project
> > > (:use :common-lisp :iter :cl-utilities)
> > > (:shadowing-import-from :iterate :collecting :collect))
> >
> > I first faced to this problem while playing to Symbolicweb. This
> > package was previously like this:
> >
> > (defpackage symbolicweb
> > (:use :common-lisp :cl-utilities)
> > or maybe
> > (:import-from :cl-utilities :collecting))
> >
> > To fix that, I'd need either modify all Lars's code. I.e., change
> > `collecting' to `cl-utilities:collecting' everywhere and so on. It was
> > impossible, of course for me as a new developer with very limited
> > "responsibility area". Making new, second package for me was not an
> > option too. Currently I'm not participating in Symbolicweb, and Lars
> > ain't using iterate still. Would he like to have this inconvinience?
> >
> > What goes to style, loop uses :keywords, iterate is promoted as a
> > substitute for loop. Why should iterate be less convinient than loop?
>
> i don't get it .. SW doesn't export the symbols `collect' or
> `collecting' ..?
>
> ,rest
> CL-USER> (require :symbolicweb)
> ..
> ..
> CL-USER> (require :iterate)
> ..
> ..
> CL-USER> (defpackage #:my-lisp-project
> (:use #:cl #:sw #:iterate)
>
> (:shadowing-import-from #:cl #:replace #:remove))
> #<PACKAGE "MY-LISP-PROJECT">
> CL-USER> (in-package #:my-lisp-project)
> MY-LISP-PROJECT> (iterate (generate i from 0 to 6)
> (collect (next i)))
> (0 1 2 3 4 5 6)
> MY-LISP-PROJECT>
>
>
> ???
>
er .. nevermind .. if you're working within the sw package itself it
imports `collect' and `collecting' from cl-utilities, yeah
hum .. and if iterate doesn't deal with this in some way or another, it
needs some changes, yeah