Peter Donald wrote:
On Thu, 30 Jan 2003 08:05, Leo Sutic wrote:I'd just like to see what you in Avalon-dev have to say about this:
Update Cocoon to latest Avalon code and remove Component from the Cocoon codebase (A 30 min job?) and the deprecation warnings will go away.
We have to provide full backward compatibility in 2.x series; all Components and Composables must be honored; core interfaces like Generator, Transformer, Serializer all extend Component and this can not be changed.
This will make sense for 3.0.
As Vadim pointed outm, OTOH, timing for such changes is really not good - we just have 3 books published recently.
From an engineering POV removing @deprecated sucks. But it's also true that from a user perspective, having deprecation warnings on core Cocoon components, ant that is all of them simce we use Avalon heavily, sucks even more.
I'm mildly in favor of removing the @deprecation tag and putting it in the docs, but I'm not sure either.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
