Timeline for JavaScript type casting
Current License: CC BY-SA 2.5
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 20, 2014 at 1:44 | comment | added | dreftymac | see also: stackoverflow.com/questions/24318654 | |
| Jan 23, 2013 at 16:26 | answer | added | BishopZ | timeline score: 0 | |
| Feb 13, 2011 at 19:59 | vote | accept | Evgenyt | ||
| Jan 7, 2011 at 17:18 | comment | added | Šime Vidas |
Or, if you want to keep things simple, just avoid type coercion altogether. There may be some good use cases for coercion (==), but as a general rule, you can just avoid it (===). And then, you can build on that rule, and add exceptions where you do want to coerce.
|
|
| Jan 7, 2011 at 14:39 | comment | added | user113716 |
When it comes to the loose == operator, the rules aren't so generic. You should read through the Abstract Equality Comparison Algorithm referenced by this answer.
|
|
| Jan 7, 2011 at 14:35 | comment | added | Evgenyt | Thanks for pointing. But not exactly, I ask for generic rules. | |
| Jan 7, 2011 at 14:26 | history | edited | Evgenyt | CC BY-SA 2.5 |
added 19 characters in body
|
| Jan 7, 2011 at 14:25 | comment | added | SLaks | possible duplicate of Why do alert(!!"0") and alert(false == "0") both output true in JavaScript | |
| Jan 7, 2011 at 14:24 | answer | added | Christian C. Salvadó | timeline score: 5 | |
| Jan 7, 2011 at 14:23 | answer | added | Šime Vidas | timeline score: 1 | |
| Jan 7, 2011 at 14:23 | answer | added | SLaks | timeline score: 8 | |
| Jan 7, 2011 at 14:22 | answer | added | Ryan Li | timeline score: 13 | |
| Jan 7, 2011 at 14:19 | history | asked | Evgenyt | CC BY-SA 2.5 |