>
> In Alain's version this would not be possible without actually
> changing code since it is directly coupled to a particular preference
> class and API.
>
> Bottom line: I think my approach is a necessity before Alain's
> preference implementation can be usefully deployed. It allows us to
> define preferences without introducing dependencies to specific
> implementations, while allowing different implementations to discover
> the same preferences.
>
> I hope this makes the conceptual difference clear.
>
> Cheers,
>   - Andreas
Sounds good,

I will definitely be adopting this in a few packages.

Keith