Wherever it makes sense, Prototype follows Ruby's general philosophy,
and that includes naming scheme. If the most confusing result is that
someone expects "unique" instead of "uniq," that's a gambit I'm
willing to make. A developer would immediately know what "uniq" means
upon reading documentation.

I have no cause to argue passionately against adding this alias, but I
feel it'd start us on the slippery slope.


On Aug 4, 8:33 pm, Jeff Watkins <[EMAIL PROTECTED]> wrote:
> Except that many users of Prototype don't use Ruby.
> On Aug 4, 2007, at 5:55 PM, Mislav Marohnić  
> <[EMAIL PROTECTED]> wrote:
> > On 8/1/07, Ken Snyder <[EMAIL PROTECTED]> wrote:
> > Unique might be specified array method in JavaScript 2.0--otherwise,
> > yes, "unique" is more intuitive than "uniq".
> > "uniq" is Ruby. IMO, there's no need to alias "unique" to it

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 

Reply via email to