I think you should have read my small comment as well I’m not insulting John but instead complimented him on the trick. The reference to developer stupidity was not directed at John but at developer in general even me when I make mistake like forgetting the ‘new’ I call myself stupid.

My comment did sound a bit firing but at the concept for a simple reason that I don’t think it will help using it as a generic method to declare your classes in this manner as the performance result will be un-acceptable in a production environment. But hey that’s just me let’s ask John if he think that increasing by approx 60% the instance creation time is acceptable?

:)

I mean, when I write :

if(myvalue=null)

instead of :

if(myvalue==null)

Nothing is telling me I’m doing something wrong, but my conditionnal is always true while this might not be the behaviour expected.
That’s why, I would write :

if(null==myvalue)

And if I’m forgotting a equal sign, I’ll get an error, that’s what errors are for, to be reported. When you do mistakes and learn from them, you’re actually improving you skills.

At least, that’s my opinion.

PS : Sorry for mistakes, I’m French, but I’m learning ;-)

First, if ‘new’ fixes things then ‘new’ is the pain free way and I’m afraid John’s suggestion is not practical.

That said, John’s code seems to also be a nifty poc at least. I think it’s pretty damn cool and appreciate getting to see/learn from it. Thx John! I agree wholeheartedly with Rey in having a big fat ? regarding the bad attitude of some in the comments.

He’s not fixing anything, but there’s still no point in doing such a thing. Maybe I’m missing something, but I can’t see how 3 letters can ease any pain.

Also, why would you attack John personally? Has he done anything to you for you to lower yourself to name-calling?

You want to have var x = new User() ? well, don’t forget the “new”, that’s all, no need for a crappy makeClass()

I share ‘Samori’ point on if the user is not doing what he should why should you clutter your code to make for there stupidity. However that said it is indeed a pretty nice trick.

Really simple benchmark example page below.
John Way:
http://lm.elmuchacho.com/library/tests/makeClass_john_resig/makeClass.htm
Native Way:
http://lm.elmuchacho.com/library/tests/makeClass_john_resig/native.htm

The result speak of itself.

That was exactly what I was thinking when reading this. It is a programmer’s error it should be covered up. This creates a debugging mess.

This misleads to horrible code design and probably future refactoring problems.

If i write a program to print “Helo World”, it should print “Helo World”, not “Hello World”, just as an example.

The more earlier an error comes out, the easier the debugging will be.