Prototyping functions coding style

Question

When protyping functions (in most code I've seen) they are generally written like so:

function MyFunc() { }
MyFunc.prototype.render1 = function() { };
MyFunc.prototype.render2 = function() { };
MyFunc.prototype.render3 = function() { };

However this can be shortened like so:

function MyFunc() { }
MyFunc.prototype = {
    render1: function() { },
    render2: function() { },
    render3: function() { }
};

From my understanding the shortended way will completely override the functions prototyped properties, as opose to adding one. Is there any other downsides to writing the protoyped functions in this manner?

Is messing up the sensible defaults of your object completely not enough of a downside? — The Paramagnetic Croissant, Sep 04 '14 at 08:31

score 1 · Answer 1 · answered Sep 04 '14 at 08:31

1

I don't know any issues writing the second way - which I use also - because root prototype is Object, and you are passing an object so...

answered Sep 04 '14 at 08:31

dmidz

896
7
20

...so you are overwriting anything that was set previously... – The Paramagnetic Croissant Sep 04 '14 at 08:39
because you extend native Object prototype ?! too bad... – dmidz Sep 04 '14 at 08:46

Prototyping functions coding style

1 Answers1