🚀 go-pugleaf

Yes. I wasn't thinking of default values...

I'm very wary of prototyping standard classes. I once created a 
prototype function on the js Object class, and it caused some 
very_difficult_to_track_down bugs in another script which happened to be 
running in the same engine. Since then, I've stayed far away from 
prototyping anything besides my own private classes...

Generally, there's no need to create a prototype method to accomplish 
the goal. Simon's example is functionally equivalent to:

function Contains(array,a)
      {
        for (var r = 0; r < array.length; r++)
          {
            if (array[r] == a) { return true; }
          }
        return false;
      }
and you just write: if(Contains(array,a)){do something...}

There's actually an advantage to not use prototyping in Simon's example: My construct can be used on any object which has a length property (like strings or collections).

Dirk's example can be done in a similar way.

This is the construct that I generally use. I think it's a lot safer (albeit slghtly harder to read) than polluting the public classes...

I don't think there's any performance gain by using prototypes here.

-- 
Harbs
http://www.in-tools.com