On Fri, 24 Feb 2012 02:24:21 -0200 Lucas De Marchi <lucas.demar...@profusion.mobi> said:
> On Thu, Feb 23, 2012 at 10:36 PM, Carsten Haitzler <ras...@rasterman.com> > wrote: > > On Thu, 23 Feb 2012 16:31:10 +0100 Leif Middelschulte > > <leif.middelschu...@gmail.com> said: > > > > actually i'm worried about deprecating functions there in 1.0 or added > > after. > > > > leif - dont deprecate the old function. we have to keep supporting it - add > > new ones, but dont start deprecating functions that are now stable > > supported api's of efl. > > Why not? > > Isn't it better to warn users since 1.x.y.z that a function is > deprecated and there's a better option available? When we decide to > bump API we can remove it and likely there will be no users of it > anymore. Less pain to the transition 1 -> 2 no problems with deprecation in general - just that we are way too early to go deprecating things - even if they stay supported for many years. it just adds warnings to code very early in a support cycle. -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
