This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
| Summary: | expected '===' and instead saw '==' | ||
|---|---|---|---|
| Product: | javascript | Reporter: | alaksundar |
| Component: | Editor | Assignee: | Petr Pisl <ppisl> |
| Status: | RESOLVED INCOMPLETE | ||
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 7.3 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Issue Type: | DEFECT | Exception Reporter: | |
|
Description
alaksundar
2012-09-11 04:18:19 UTC
I'm sorry, I don't understand what is the problem. Please specify more. Why requires '===' instead of '==' ??? 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. |