4 Sep
2008
4 Sep
'08
10:58 a.m.
Hi Alex,
This is not really a bug, it is just what the code generator from the
information it has.
The reason for why it is not implemented is the following. We wanted
to keep belongsTo because it is like a trademark for FAMIX :), but on
the other hand it would be nice if a method has a parentClass. So, in
FAMIX 3.0 belongsTo, is derived from whatever implementation there is
for the different classes.
So, for FAMIXMethod, belongsTo should return parentClass. For
FAMIXClass, belongsTo should return parentScope.
Because we cannot encode this information in FM3, the decision was to
just generate self shouldImplement. The rest should be done by hand.
Cheers,
Doru
On Sep 4, 2008, at 10:04 AM, Alexandre Bergel wrote:
Hi!
Is the following method the way it should be?
-=-=-=-=-=-=-=-=-=-=-=-=
FAMIXNamedEntity>>belongsTo
<MSEProperty: #belongsTo type: #FAMIXContainerEntity> <derived>
"This stub-code was automatically generated. Please fill in."
self notImplemented
-=-=-=-=-=-=-=-=-=-=-=-=
When I run the following code, I get a rollback on this
notImplemented:
-=-=-=-=-=-=-=-=-=-=-=-=
| class |
class := FAMIXClass new.
class name: 'AClass'.
class addToMethods: (FAMIXMethod new name: 'aMethod'; yourself).
class addToMethods: (FAMIXMethod new name: 'anotherMethod';
yourself).
(class mooseDescription allAttributes detect: [:p | p name ==
#belongsTo]) getFrom: class
-=-=-=-=-=-=-=-=-=-=-=-=
Any idea ?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
www.tudorgirba.com/blog
"Problem solving should be concentrated on describing
the problem in a way that is relevant for the solution."