On Wed, 10 Jul 2002 19:55, Carsten Ziegeler wrote: > Peter Donald wrote: > > > Why do you want to aquire the store even if it is not used? > > > > Basically to avoid warnings in a container I am working on. ie If > > you declare > > dependencies (even if they are optional dependencies) and the container > > provides you component but you dont use it then the container > > will wanr you > > saying something like > > > > "You have misdeclared a dependency on X as it was never used." > > > > or similar. > > Hmmm, I'm not sure if this is a good feature - because an optional > dependency means it's - well - optional. And I see two use cases > their: > a) The optional component is only used if it is available
thats the usecase I had in mind. > b) The optional component is used only in some circumstances That is the usecase that I originally liked but Berin jumped on me back in ye old days for it. Then we both jumped on Fede (one of the original avalon developers). Whats everyone else think. Should optional dependencies be "optional" depending on the presence of some attribute (be it config variable or something). Or should it be the assemblers decision, ie If they provide the component then it is used else it is not. -- Cheers, Peter Donald "The ability to quote is a serviceable substitute for wit." -- Maugham -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
