Avoiding "new anonfn"

noanon.md

JSLint doesn't like using new function. This makes sense, because you're just creating a singleton, and so there's no point in using a constructor for that. If you have something like this:

var NowWithClosures = Backbone.Model.extend(new function(){
    var x = 1;
    this.initialize = function(){
        console.log('init');
    };
    this.AddOneToX = function(){
        x++;
    };
    this.getX = function() {
        return x;
    };
});

var nwc = new NowWithClosures();
nwc.AddOneToX();
console.log(nwc.getX());

You can easily rewrite using the module pattern like this:

var NowWithClosures = Backbone.Model.extend((function(){
    var x = 1;

    return {
        initialize: function(){
            console.log('init');
        },
        AddOneToX: function(){
            x++;
        },
        getX: function() {
            return x;
        }
    };
}()));

var nwc = new NowWithClosures();
nwc.AddOneToX();
console.log(nwc.getX());

Now, you're avoiding the weird new function thing and don't have to worry about this at all.

Thanks

I didn't know devs were picking up the new function(){} usage.
I kinda dig it and could care less about what JSLint complains about.

I've been using new function() for a while instead of object literals as I like semicolons more than commas, and I like being able to execute code inside my function creation/definitions.

@ws-emberex Cool. I'm guilty of forgetting about it, but was just reminded about it earlier today in an unrelated snippet.

I updated my sublime text settings:
"jshint_options": { "supernew": true }