Lines Matching full:confusing
110 <tr bgcolor="#ffffff"><td><a href="#NM_CONFUSING">Nm: Confusing method names</a></td><td>Bad practice</td></tr>
117 <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>
248 <tr bgcolor="#ffffff"><td><a href="#NM_VERY_CONFUSING">Nm: Very confusing method names</a></td><td>Correctness</td></tr>
1007 be confusing to users of this class.</p>
1010 <h3><a name="NM_CONFUSING">Nm: Confusing method names (NM_CONFUSING)</a></h3>
1054 This can be exceptionally confusing, create lots of situations in which you have to look at import statements
1065 This can be exceptionally confusing, create lots of situations in which you have to look at import statements
1071 <h3><a name="NM_VERY_CONFUSING_INTENTIONAL">Nm: Very confusing method names (but perhaps intentional) (NM_VERY_CONFUSING_INTENTIONAL)</a></h3>
1075 This is very confusing because if the capitalization were
1077 seems that the existence of both of these methods is intentional, but is sure is confusing.
1110 so this is presumably understood. However, such methods are exceptionally confusing. You should strongly consider
1608 and it is at least confusing.
1816 less confusing to explicitly check pointer equality using <code>==</code>.
2358 instance field in a superclass. This is confusing, and
2581 <h3><a name="NM_VERY_CONFUSING">Nm: Very confusing method names (NM_VERY_CONFUSING)</a></h3>
2585 This is very confusing because if the capitalization were
3554 The existing code might be OK, but it is confusing and a
3557 throughout the JVM, leading to very confusing behavior and potential deadlock.
3668 your design, as other developers will find it exceptionally confusing.
4679 is final, it can not be derived from, and the use of protected is confusing. The access
