You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As interfaces do not contain any logic and consequently attribute accesses, include them in LCOM calculation is not relevant.
Currently the overall LCOM result is distorted, and does not reflect the reality.
Maybe interfaces should be excluded from LCOM calculation or at least should not influence the result.
Eric
The text was updated successfully, but these errors were encountered:
Thanks, but I'm not pretty sure removing getters and setters is a good idea.
They are functions and so can do much more than what they are simply supposed to.
Furthermore any function can play the role of a property accessor.
IMHO, it seems to me a little bit risky to go in that way...
According to me, LCOM is useful because it reflects responsabilities of class. Maybe we need a new metrics, LCOM5 = LCOM4 without getters and setters...
As interfaces do not contain any logic and consequently attribute accesses, include them in LCOM calculation is not relevant.
Currently the overall LCOM result is distorted, and does not reflect the reality.
Maybe interfaces should be excluded from LCOM calculation or at least should not influence the result.
Eric
The text was updated successfully, but these errors were encountered: