"Leslie P. Polzer" <[email protected]> writes: > On Jan 13, 12:09 pm, Jan Rychter <[email protected]> wrote: >> Well, what I did with my code was almost a search-replace, you basically >> need to: > > Good, this will serve as a migration guide that will accompany the > next release. > >> What I initially wanted was to have a (setf (my-children x) children) >> and (my-children x) thing, which would automatically determine the type >> of x and use it as a key. It might be possible to do and it would make >> the interface somewhat nicer -- but I'd still want to keep the >> {get|set}-children-of-type methods, because I have widgets that maintain >> two or three lists of children > > So are you going to implement this convenience interface? > I would like to have this.
Could be done -- but I'd rather first finish the discussion with Stephen, as his approach might turn out to be better and the whole issue might become moot :-) [...] > Yeah, let's worry about it later. > >> You can supply arguments to (setf) functions? > > Works fine around here. ;) Oh -- the 'place' form can take optional arguments -- I didn't know that. That could indeed be used. > How about the tests? Have you written tests for your new nav system > and/or adapted the current tests? No, of course not -- there is no point unless we agree on the general design. If I spend time on fixing/writing tests now, and my design never gains any acceptance, the effort would be wasted. --J. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
