Re: [Gnu-arch-users] PyArch newbie observations/questions

[Aaron Bentley]

More thoughts

David Allouche wrote:
> On Sat, May 29, 2004 at 12:40:20AM -0400, Aaron Bentley wrote:
>
> > Good grief.  This has been banging around inside the gnu mail system for 
> > 3 days!  Feel free to use reply-all to me.
>
>
> Are you in such a hurry?

Well, you told me about the post on IRC, and then I kept wondering about 
it...

> > It seems to me that we'd want a per change iterator.
>
>
> I was rather thinking about a more general mechanism for methods which
> provide incremental output one could want to monitor. For example
> library-add and changeset-applying functions.
>
> The per-change iterator makes sense for CHANGES, but it would be the
> function-specific layer.

Here's my latest thoughts:  All functions can return itererators for 
their output.  But the iterators can return various types.

All iterators could return Chatter objects (the "* yada ydada" 
messages).  In addition, the CHANGES iterator would return objects 
derived from FileChange.  The INVENTORY iterator would return Chatter 
and FileClass iterators.  The TREE-LINT iterator would return 
LintViolation objects.

All of these would be easily convertable to text, or could provide 
access to program-usable data (FileMove would have the old and new 
names, for example).

Higher-level iterators could be built on top of these, to allow 
filtering, e.g. so that Chatter could be ignored when not wanted.

Aaron