Giacomo Pati wrote:
Daniel Fagerstrom wrote:
Giacomo Pati skrev:
Daniel Fagerstrom wrote:
Giacomo Pati skrev:
Again, how should deprecation be implemented:
a) use deprecation logger but keep current implementation
b) throw an exception and remove current implementation
a) is probably the correct solution, but at least I would prefer b). To
me, the class attribute in forms for creating components seem like some
hack or workaround that hopefully very few depends on.
I think we should vote on this, shouldn't we? I absolutely dislike having the
LifecycleHelper (and
thus Avalon classes) staying in the CForms code.
What do otehrs think about it?
I don't like them either. I would vote +1.
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
