>
> I don't see why we would need the num_levels parameters too. We
> could probably have just two iterators, one which gets all attributes,
> including inherited attributes, and once which gets only the local
> attributes. Does this sound reasonable? Also, when someone tries to
> delete inherited attributes, we could do the checking iff the call is
> made through the interface. This is a very good example, of why iterators
> are better.
>
> -jk
>
I took the idea of num_levels from ir.idl from Orbeline. I am not quite sure
when one would like that, so if you don't see a reason either, let's not have
it.
I think only one iterator is needed. The method in the interface would be
declared something like
Attribute_Iter attribute_iter(in bool inherited);
So, if a client gets the iterator with TRUE, the iterator will let them
traverse all attributes. Otherwise only the local ones.
Pedro Szekely
USC/ISI, 4676 Admiralty Way, Marina del Rey, CA 90292
Phone: 310/822-1511, Fax: 310/823-6714
URL: http://www.isi.edu/isd/HUMANOID-HOME.html