Regarding the "Add instance variables" critic that does sound like a defect (the wording and the fact it appears at all). Please create an issue in issuezilla.
With your attachment I see no critic suggesting a utility. I think it should only do that if all operations are static. If you see any issues like this feel free to just go right ahead and create the relevant issues explaining how to reproduce. Regards Bob 2009/6/28 Olivier Cailloux <[email protected]>: > Dear list, > > I notice that when considering a class containing only frozen > attributes, argo (0.28) suggests defining it as utility or defining > instance variables. I don't understand this advice, is it adequate? > IMHO, a frozen attribute is an instance attribute anyway (why does it > talk about a "variable" btw?). And I don't think that the utility > stereotype applies to entities, i.e. model objects, even if they are > immutable. See hereby a sample xmi and zargo project, and below an > example java class, which trigger the critic. > > package argo.simple; > > public class ValueContainer { > private final int m_value; > > public ValueContainer(int value) { > m_value = value; > } > > public int getValue() { > return m_value; > } > > } > > Please tell me if I am misunderstanding something. > Olivier > > ------------------------------------------------------ > http://argouml.tigris.org/ds/viewMessage.do?dsForumId=449&dsMessageId=2366069 > > To unsubscribe from this discussion, e-mail: > [[email protected]]. ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=449&dsMessageId=2366090 To unsubscribe from this discussion, e-mail: [[email protected]].
