cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicola Ken Barozzi <>
Subject Re: defaulting to a matcher when another one is not present
Date Sat, 12 Oct 2002 23:34:45 GMT

Hunsberger, Peter wrote:
>>>Umm, forgot to comment on this: if I invoke another classes methods I'm
>>>certainly free to deal with any exception as I see fit? It seems to me
>>>a sitemap doesn't implement the equivalent of composition either...
>>A sitemap is not a class either, it doesn't have methods.
>>The analogy is not 1-1, but the concept remains: inheritance would mean 
>>I get all the matchers of the supersitemap plus mine and eventually 
>>substitute then, while composition means I can compose subsitemaps in a 
>>parent sitemap and make them handle part of the URI space.
> But that still doesn't explain why you shouldn't be free to catch or ignore
> exceptions from the sub sitemap as you see fit?  

In this answer I was talking about the analogy.

> I will note that inheritance doesn't mean you get exactly the matchers of a
> "supersitemap".  Rather, you can choose to override them or not, as you see
> fit.  Of course, having used Smalltalk before I ever encountered Java I
> don't see anything wrong with inheritance (or for that matter multiple
> inheritance)...

And I don't see the need for inheritance yet.
The only example you gave is about using a hack to circumvent sloppy URI 
usage, which doesn't look like a feature to me.

Maybe inheritance is a killer feature, maybe it will be essential in 
blicks, but you have yet to give me the use case.

Nicola Ken Barozzi         
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)

To unsubscribe, e-mail:
For additional commands, email:

View raw message