13 Nov
2011
13 Nov
'11
11:09 p.m.
This is not an issue. I do not write on what I do not know.
I'm now trying to get a document in PDF about FAMIX30.
My goal is to make part of the implicit explicit and iterate. HEnce my focus on class
comment.
Stef
I do not understand. This was a todo for me to know
that I should document the discussions that went around when we worked on FAMIX. Why is
this an issue?
Doru
On 13 Nov 2011, at 22:11, Stéphane Ducasse wrote:
Ok since I do not know the conventions and I
guess nobody except you knows them I will not write about them in my document.
Entry closed.
Stef
On Nov 13, 2011, at 9:30 PM, Tudor Girba wrote:
--
www.tudorgirba.com
"Obvious things are difficult to teach."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev It means that I would like to tell people how the
names of the instance variables in FAMIX should be read. For example, if we have an
association from Class to Method, then the instance variable in class is named
"methods". Things like this.
Doru
On 13 Nov 2011, at 20:20, Stéphane Ducasse wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Hi
in http://www.themoosebook.org/book/internals/famix/core/overview
there is todo
naming convention for attributes
what does it means?
naming convention for classes, package, methods, attributes?
Stef
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Every thing has its own flow."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev