> From: Paul Hammant [mailto:[EMAIL PROTECTED]] > > > WARNING: A component that specifies this requirement will not > > be as portable as one that doesn't. Few containers > > support it. It is therefore discouraged for components > > to require a castable context.
> If this is a phrase for the future (when Phoenix has been > replaced by UberContainer), *No.* The �ber is a big unknown at the moment. Will it be A4 compliant? Will it be so via a compatibility layer? Will it have A5 features? What will those be? And so on... Once the �ber has been created, and we have nailed down the different profiles (if any), I expect this contract to change. But that's a bit in the future, thus a warning based on the current state of Avalon is valid. If the �ber *does* have very good support for castable contexts, or if we get such features in many containers, we can just remove the warning. If not, we let it remain. > Otherwise +1 Noted your +1. I hope I answered your question and that you are satisfied with the reply. /LS -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
