[Grok-dev] Traversing

[Christian Theune]

Hi,

Martijn Faassen wrote:
> Philipp von Weitershausen wrote:
>> Christian Theune wrote:
> 
>>> The most simple solution I can imagine would be to define a default
>>> traverse() on the container that does the dict lookup.
>>
>> That's a good solution.
> 
> Hm, I think I disagree.
> 
>  I think in general objects should have whatever traversal behavior they
> do normally, and let traverse() be available for override. We don't want
> to *reimplement* its normal traversal behavior with traverse.

So our custom traverser would check whether we define traverse. If we
do: call it. If not: defer to the "original" traverser?

Philipp: Is there a way in the CA to express this?

Christian

-- 
gocept gmbh & co. kg - forsterstraße 29 - 06112 halle/saale - germany
www.gocept.com - ct at gocept.com - phone +49 345 122 9889 7 -
fax +49 345 122 9889 1 - zope and plone consulting and development


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 252 bytes
Desc: OpenPGP digital signature
Url : http://mail.zope.org/pipermail/grok-dev/attachments/20061020/a80297c3/signature.bin