I know that jslint is only a recomendation and that it's intended to be used to spot bad JS code, but it's still a good tool to use to pre-qualify and sanity check your code in an automated build/test environment. As I wrote, I'm interested in workarounds to make the code pass jslint, not avoid running jslint at all.
JSLint is only a guide, you don't always have to adhere to the rules. The thing is, you're not creating functions in a loop in the sense that it's referring to. You only create your classes once in your application, not over and over again.
Of course, those solutions are obvious. The point remains, you're still creating functions inside the loop, you've just written it in a particular way that is arguably more convoluted, just to appease some tool. Whatever, if that's what you want to do, go for it.
Sure, but if you look at the answer below, you're still making a function in a loop. You're adding extra code just to appease JSLint. Why would you do this?