That's in for backwards compatibility. For stuff like this, we'd need some way of marking things as deprecated, giving a warning that it "will be removed in next major version".
I can imagine an optional deprecated.js file to load in while doing development, that gives console.log warnings (or so) whenever you use deprecated Prototype methods, so you can check your code if something needs to be changed. Best, Thomas Am 14.02.2007 um 09:01 schrieb Mislav Marohnić: > On 2/14/07, Colin Mollenhour <[EMAIL PROTECTED]> wrote: > > 1686 var Toggle = new Object(); > 1687 Toggle.display = Element.toggle; > > What is the point of this? > > It's a shortcut that's supposed to look nice while writing: > > Toogle.display ("foo") > > I don't like it, though, and also agree that it pollutes the global > namespace. > > +1 for removing it. That makes two of us now. > > > -- Thomas Fuchs wollzelle http://www.wollzelle.com questentier on AIM madrobby on irc.freenode.net http://www.fluxiom.com :: online digital asset management http://script.aculo.us :: Web 2.0 JavaScript http://mir.aculo.us :: Where no web developer has gone before --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype: Core" group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en -~----------~----~----~----~------~----~------~--~---