23 Nov
2007
23 Nov
'07
8:42 a.m.
So in that case we should rename to two to mooseName.
Which is also ok for me.
Stef
That is true. We can rename it to mooseName.
Doru
On Nov 22, 2007, at 10:36 PM, Adrian Kuhn wrote:
Please do the other way round, kick
mooseUniqueName and make
absoluteFamixName the default. Names are not unique in Moose for
several reasons. Actually that method should have been removed/
renamed long time ago, as its name is dangerously misleading...
AA
On 22 Nov 2007, at 21:34 , Stéphane Ducasse wrote:
--
www.tudorgirba.com
www.tudorgirba.com/blog
"From an abstract enough point of view, any two things are similar."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
absoluteFamixName
could we use instead mooseUniqueName and deprecated
absoluteFamixName
This way we could manupilate classes and famixClass a bit the same
way
Stef
On 22 nov. 07, at 15:49, stephane ducasse wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi
How can I get the moose name of a smalltalk class?
I tried mooseUniqueName
Point mooseUniqueName
Stef
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev