Chris McDonough wrote: > Martijn Faassen wrote: [snip] >> Sometimes you can only test a library when a particular utility or >> adapter or event handler is registered. The library uses this utility or >> adapter in its own logic and while the utility or adapter is intended to >> be replaceable (to make the library pluggable), it is mandatory to >> actually register a component that fulfills the interface requirements >> in order to use the library at all. > > Can you provide an example? In my own libraries, very rarely does this > happen; > I tend to only depend on components like this "at the edges"; eg. in I only > try > to allow pluggability via the CA within an application or a framework, very > rarely in a straight library.