Bug 218091 - expected '===' and instead saw '=='
expected '===' and instead saw '=='
Status: RESOLVED INCOMPLETE
Product: javascript
Classification: Unclassified
Component: Editor
7.3
PC Windows 7
: P3 (vote)
: TBD
Assigned To: Petr Pisl
issues@javascript
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-09-11 04:18 UTC by alaksundar
Modified: 2013-03-05 09:23 UTC (History)
0 users

See Also:
Issue Type: DEFECT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description alaksundar 2012-09-11 04:18:19 UTC
if (j == 'n')
Comment 1 Petr Pisl 2012-09-11 07:39:01 UTC
I'm sorry, I don't understand what is the problem. Please specify more.
Comment 2 alex_torfan 2013-03-04 09:02:51 UTC
Why requires '===' instead of '==' ???
Comment 3 Petr Pisl 2013-03-05 09:23:32 UTC
Because it's JavaScript good practice. Quotation from JsLint documentation:

The == and != operators do type coercion before comparing. This is bad because it causes ' \t\r\n' == 0 to be true. This can mask type errors. JSLint cannot reliably determine if == is being used correctly, so it is best to not use == and != at all and to always use the more reliable === and !== operators instead.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo