deprecated('1.0.2', "such and such is deprecated') ... and it gets
removed from the packed/production version, and left in to log in the
junior-developer-edition.
On 10/15/06, Jörn Zaefferer <[EMAIL PROTECTED]> wrote:
> Ⓙⓐⓚⓔ schrieb:
> > I feel there are too many names for the ajax functions.... they can
> > all be coded ajax.. and some share names with non ajax function (as
> > John mentioned)... perhaps new names for these weirdly overloaded
> > functions?
> >
> Good point. Having a common prefix for all ajax related methods could be
> a big help.
> > Which brings up the matter of deprecating... it would be helpful if
> > you use a function in an old manner, you could get a deprecated
> > message in the log
> >
> I don't think we should use deprecation in a library that depends
> heavily on file size. You never know when the time has come to actually
> remove that crap, therefore it sticks there for all time. Great ugly
> example: The Java runtime enviroment (JRE). It gets bigger with every
> release, but never smaller (though this may actually change).
> I think branching may hurt more at first, but help a lot to evolve the
> API while maintaining stable releases.
>
> -- Jörn
>
> _______________________________________________
> jQuery mailing list
> [email protected]
> http://jquery.com/discuss/
>
--
Ⓙⓐⓚⓔ - יעקב ʝǡǩȩ ᎫᎪᏦᎬ
_______________________________________________
jQuery mailing list
[email protected]
http://jquery.com/discuss/
