4 Sep
2008
4 Sep
'08
1:15 p.m.
It does not work.
Doiting:
FAMIX2Class mooseDescription
leads to a debugger...
Alexandre
On 4 Sep 2008, at 11:50, Stéphane Ducasse wrote:
Load the latest version of moose
and do
MooseModel2 resetMetaDescriptions.
(FMRepository with: MooseModel2 meta).
Stef
On Sep 4, 2008, at 11:22 AM, Bergel, Alexandre wrote:
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
The image froze because moosePrintOn: called
belongsTo, and it uses
an
assertion to check that belongsTo is notNil. moosePrintOn: is called
by printOn:, which loops in a debugger.
For now, FAMIX2Class cannot be browsed since asMooseDescription does
not work. The following code leads to an error:
| class |
class := FAMIX2Class new.
class setName: 'AClass'.
class addMethod: (FAMIX2Method new setName: 'aMethod'; yourself).
class addMethod: (FAMIX2Method new setName: 'anotherMethod';
yourself).
class mooseDescription.
The reason is that the instance of FMMetaRepository has an instance
variable named classDict, which contains as keys the FAMIX3 classes,
and not the ones of the version 2.
This looks like to be very deep in the fame, famix3, meta blob. I do
not know what should be done to fix this.
Cheers,
Alexandre
On 4 Sep 2008, at 11:00, Tudor Girba wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Actually, at the time I did work with FAMIXClass,
not FAMIX2Class
because FAMIX2 was not described in Fame yet.
But it should work with FAMIX2 now as well. Does it still freeze
with
FAMIX code only?
Cheers,
Doru
On Sep 4, 2008, at 10:52 AM, Bergel, Alexandre wrote:
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
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 I should have written:
| class |
class := FAMIX2Class new.
class setName: 'AClass'.
class addMethod: (FAMIX2Method new setName: 'aMethod'; yourself).
class addMethod: (FAMIX2Method new setName: 'anotherMethod';
yourself).
(replaced addToMethods: by addMethod:)
But it is still interesting why it blocks the image. It has to do
with
BlockContext.
Cheers,
Alexandre
On 4 Sep 2008, at 10:31, Alexandre Bergel wrote:
> Hi again,
>
> Doru, last week you wrote a small class definition for the
> MooseFinder.
>
> | class |
> class := FAMIXClass new.
> class name: 'AClass'.
> class addToMethods: (FAMIXMethod new name: 'aMethod'; yourself).
> class addToMethods: (FAMIXMethod new name: 'anotherMethod';
> yourself).
>
> Remember?
> I guess this should be the FAMIX 2 version of these 5 lines of
> code:
>
> | class |
> class := FAMIX2Class new.
> class setName: 'AClass'.
> class addToMethods: (FAMIX2Method new setName: 'aMethod';
> yourself).
> class addToMethods: (FAMIX2Method new setName: 'anotherMethod';
> yourself).
>
> However it lamentably open debugger that cannot be closed. The
> image
> is unusable.
>
> 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
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
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
"When people care, great things can happen."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev