Martijn Faassen wrote at 2007-10-24 18:38 +0200:
> ...
>disagree with the position that should not ever treat an adapter
>registration as an implementation detail to provide some default
>behavior. Sometimes the behavior of a library *relies* on certain
>adapters being registered. An example is an adapter registration to
>generate an appropriate error message (if no more specific adapters
>are registered by the user of the library).

But requiring that a more specific adapter must be registered can
be a bit tedious -- as it may require to define an additional (and unnatural)
interface that derives from the original one -- just to be able
to register a more specific adapter...

Zope-Dev maillist  -
**  No cross posts or HTML encoding!  **
(Related lists - )

Reply via email to