16 lines
830 B
Plaintext
16 lines
830 B
Plaintext
|
=== On 2014-10-12T17:00:01Z Freddy Mallet Wrote:
|
||
|
|
@Ann, when discovering this rule it was not obvious for me to understand if there was or not a difference between self:: or static:: prefixes to access static functions of fields.
|
||
|
|
|
||
|
|
|
||
|
|
If my understanding is correct, there is no difference but obviously it's better to use static:: to prevent any misunderstanding.
|
||
|
|
|
||
|
|
|
||
|
|
If this is the case, I would associate this rule to the SQALE characteristic Maintainability > Understandability and to the tag pitfal
|
||
|
|
|
||
|
|
=== On 2014-10-14T14:43:05Z Ann Campbell Wrote:
|
||
|
|
\[~freddy.mallet] I disagree about SQALE - the point of the rule is that when you use ``++self::++`` you're going to get the superclass' version, not the override - i.e. you won't get what you think you will.
|
||
|
|
|
||
|
|
=== On 2014-10-21T20:29:24Z Ann Campbell Wrote:
|
||
|
|
\[~linda.martin] LGTM
|
||
|
|
|