5

I remember reading some "funny" examples once of weird results JavaScript can give when you, for example, add strings to numbers etc. Does anyone have any good examples or a link to the blog that I might have read them on? Which ones are likely to catch a programmer out in the real world?

closed as too broad by user40980, durron597, user53019, user22815, Dan Pichelman Jul 9 '15 at 19:14

Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • 2
    Welcome to Programmers. This questions does not meet the guidelines to asking questions on this site. Please read the site's FAQ and edit it to meet more of those guidelines. This question would fit under mindless social fun and one that creates lists for answers, both of which are off-topic. – Walter Feb 1 '11 at 13:00
8

All the ones that are described in:

  • 1
    That WAT talk is hysterical! Thanks for posting that – Avrohom Yisroel Sep 6 at 14:56
4

The biggest gotcha in JavaScript is that the == operation performs type type coercion and should almost always be avoided. Instead you should use the === to do a true boolean comparison.

For example, because of type coercion., 1 == true is true, but 1 === true is false. The == operator often hides type errors.

As a further illustration of true and false in this context these cases From Crockford's The Elements of JavaScript Style are illustrative.

'' == '0' // false    
0 == '' // true
0 == '0' // true

false == 'false' // false 
false == '0' // true

false == undefined // false 
false == null // false 
null == undefined // true

' \t\r\n ' == 0 // true
  • I would not go so far as to say 'almost always' but yes, you should definitely prefer === unless you have a sensible use for == – Erik Reppen Aug 22 '12 at 0:04
2

I would go get a copy of Douglas Crockford's Javascript the Good Parts. Its probably the best book on Javascript in terms of pointing out the parts of javascript that are good and those tha should be avoided at all costs.

Not the answer you're looking for? Browse other questions tagged or ask your own question.