Lines Matching full:confusing
105 <tr bgcolor="#ffffff"><td><a href="#NM_CONFUSING">Nm: Confusing method names</a></td><td>Bad practice</td></tr>
112 <tr bgcolor="#eeeeee"><td><a href="#NM_VERY_CONFUSING_INTENTIONAL">Nm: Very confusing method names (but perhaps intentional)</a></td><td>Bad practice</td></tr>
239 <tr bgcolor="#ffffff"><td><a href="#NM_VERY_CONFUSING">Nm: Very confusing method names</a></td><td>Correctness</td></tr>
964 be confusing to users of this class.</p>
967 <h3><a name="NM_CONFUSING">Nm: Confusing method names (NM_CONFUSING)</a></h3>
1011 This can be exceptionally confusing, create lots of situations in which you have to look at import statements
1022 This can be exceptionally confusing, create lots of situations in which you have to look at import statements
1028 <h3><a name="NM_VERY_CONFUSING_INTENTIONAL">Nm: Very confusing method names (but perhaps intentional) (NM_VERY_CONFUSING_INTENTIONAL)</a></h3>
1032 This is very confusing because if the capitalization were
1034 seems that the existence of both of these methods is intentional, but is sure is confusing.
1067 so this is presumably understood. However, such methods are exceptionally confusing. You should strongly consider
1555 and it is at least confusing.
1763 less confusing to explicitly check pointer equality using <code>==</code>.
2282 instance field in a superclass. This is confusing, and
2505 <h3><a name="NM_VERY_CONFUSING">Nm: Very confusing method names (NM_VERY_CONFUSING)</a></h3>
2509 This is very confusing because if the capitalization were
3462 The existing code might be OK, but it is confusing and a
3465 throughout the JVM, leading to very confusing behavior and potential deadlock.
3576 your design, as other developers will find it exceptionally confusing.
4542 is final, it can not be derived from, and the use of protected is confusing. The access
