Difference between revisions of "Poor Style: Confusing Naming"
From OWASP
Weilin Zhong (talk | contribs) |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | {{ | + | {{template:CandidateForDeletion}} |
| − | |||
| − | + | #REDIRECT [[Failure to follow guideline/specification]] | |
| − | + | ||
| + | |||
| + | Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}''' | ||
==Description== | ==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. | 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. | ||
| − | ==Examples == | + | ==Risk Factors== |
| + | |||
| + | TBD | ||
| + | |||
| + | ==Examples== | ||
<pre> | <pre> | ||
| Line 21: | Line 28: | ||
</pre> | </pre> | ||
| − | |||
| − | ==Related Attacks== | + | ==Related [[Attacks]]== |
| + | |||
| + | * [[Attack 1]] | ||
| + | * [[Attack 2]] | ||
| + | |||
| + | |||
| + | ==Related [[Vulnerabilities]]== | ||
| + | |||
| + | * [[Vulnerability 1]] | ||
| + | * [[Vulnerabiltiy 2]] | ||
| + | |||
| + | ==Related [[Controls]]== | ||
| − | + | * [[Control 1]] | |
| + | * [[Control 2]] | ||
| − | |||
| − | == | + | ==Related [[Technical Impacts]]== |
| − | [[ | + | * [[Technical Impact 1]] |
| + | * [[Technical Impact 2]] | ||
| − | |||
| − | + | ==References== | |
| − | + | TBD | |
Latest revision as of 23:30, 7 April 2009
#REDIRECT Failure to follow guideline/specification
Last revision (mm/dd/yy): 04/7/2009
Contents
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
