Berin Loritsch wrote:
And leads us to mark this usage pattern as "deprecated" and suggest a portable design... which we still have to agree on though.From: Leo Sutic [mailto:[EMAIL PROTECTED]]From: Leo Simons [mailto:[EMAIL PROTECTED]]
ah. ok. So a component author declares "I need a T context" and the container says "don't have one, so I'm not runningyou". Cool. Exactly. All it does is provide a method for component authors to declare their requirements (so that a container *may* satisfy them if it can and wants to) in a uniform way. Which in effect discourages this type of use if the component author values component reuse. Just from a practicality standpoint.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
