This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "Poor Style: Confusing Naming"
From OWASP
| Line 3: | Line 3: | ||
#REDIRECT [[Failure to follow guideline/specification]] | #REDIRECT [[Failure to follow guideline/specification]] | ||
| − | |||
| − | |||
| − | |||
Latest revision as of 23:30, 7 April 2009
#REDIRECT Failure to follow guideline/specification
Last revision (mm/dd/yy): 04/7/2009
Description
The class contains a field and a method with the same name.
It is confusing to have a member field and a method with the same name. It makes it easy for a programmer to accidentally call the method when attempting to access the field or vice versa.
Risk Factors
TBD
Examples
public class Totaller {
private int total;
public int total() {
...
}
}
Related Attacks
Related Vulnerabilities
Related Controls
Related Technical Impacts
References
TBD
