8:40 p.m.
Hi,
I stumble (again) into the same problem.
When importing from an MSE file, I get a MNU exception for
#accessedByList on the FAMIXNamespace UNKNOWN_NAMESPACE.
Is this something you are aware of?
I run on top of the latest MooseDevelopment (loaded Moose Config).
Thanks,
Ricky
11:15 a.m.
Hi ricky
do you arrive to describe a bit better your problem?
Reducing it so that we know if the problem comes from the importer or
the exporter.
Stef
On Jul 21, 2008, at 8:40 PM, Richard Wettel wrote:
Hi,
I stumble (again) into the same problem.
When importing from an MSE file, I get a MNU exception for
#accessedByList on the FAMIXNamespace UNKNOWN_NAMESPACE.
Is this something you are aware of?
I run on top of the latest MooseDevelopment (loaded Moose Config).
Thanks,
Ricky
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
12:21 p.m.
Hi Stef,
When I do the import, it does the file reading and importing X
elements phases, and during the "importing attributes and
associations" it throws a Message not understood: #accessedByLists on
an instance of FAMIXNamespace (#UNKNOWN_NAMESPACE). The problem seems
to be that #accessedByLists is defined in
FAMIXAbstractStructuralEntity and FAMIXNamespace is not a subclass of
it, but of FAMIXAbstractScopable. Maybe the meta-definition of
"access" is the problem.
Ricky
On Jul 23, 2008, at 11:15 AM, Stéphane Ducasse wrote:
Hi ricky
do you arrive to describe a bit better your problem?
Reducing it so that we know if the problem comes from the importer or
the exporter.
Stef
On Jul 21, 2008, at 8:40 PM, Richard Wettel wrote:
> Hi,
>
> I stumble (again) into the same problem.
> When importing from an MSE file, I get a MNU exception for
> #accessedByList on the FAMIXNamespace UNKNOWN_NAMESPACE.
>
> Is this something you are aware of?
>
> I run on top of the latest MooseDevelopment (loaded Moose Config).
>
> Thanks,
> Ricky
> _______________________________________________
> 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
3:18 p.m.
Hi all,
The problem arose when referencing a namespace.
Doru just fixed this problem in version 3.2.113 of MooseDevelopment.
Thanks, Doru!
Cheers,
Ricky
On Jul 23, 2008, at 12:21 PM, Richard Wettel wrote:
Hi Stef,
When I do the import, it does the file reading and importing X
elements phases, and during the "importing attributes and
associations" it throws a Message not understood: #accessedByLists on
an instance of FAMIXNamespace (#UNKNOWN_NAMESPACE). The problem seems
to be that #accessedByLists is defined in
FAMIXAbstractStructuralEntity and FAMIXNamespace is not a subclass of
it, but of FAMIXAbstractScopable. Maybe the meta-definition of
"access" is the problem.
Ricky
On Jul 23, 2008, at 11:15 AM, Stéphane Ducasse wrote:
> Hi ricky
>
> do you arrive to describe a bit better your problem?
> Reducing it so that we know if the problem comes from the importer or
> the exporter.
>
> Stef
>
> On Jul 21, 2008, at 8:40 PM, Richard Wettel wrote:
>
>> Hi,
>>
>> I stumble (again) into the same problem.
>> When importing from an MSE file, I get a MNU exception for
>> #accessedByList on the FAMIXNamespace UNKNOWN_NAMESPACE.
>>
>> Is this something you are aware of?
>>
>> I run on top of the latest MooseDevelopment (loaded Moose Config).
>>
>> Thanks,
>> Ricky
>> _______________________________________________
>> 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
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
8:53 p.m.
doru what was the problem in a nutshell?
Stef
On Jul 23, 2008, at 3:18 PM, Richard Wettel wrote:
Hi all,
The problem arose when referencing a namespace.
Doru just fixed this problem in version 3.2.113 of MooseDevelopment.
Thanks, Doru!
Cheers,
Ricky
On Jul 23, 2008, at 12:21 PM, Richard Wettel wrote:
> Hi Stef,
>
> When I do the import, it does the file reading and importing X
> elements phases, and during the "importing attributes and
> associations" it throws a Message not understood: #accessedByLists on
> an instance of FAMIXNamespace (#UNKNOWN_NAMESPACE). The problem seems
> to be that #accessedByLists is defined in
> FAMIXAbstractStructuralEntity and FAMIXNamespace is not a subclass of
> it, but of FAMIXAbstractScopable. Maybe the meta-definition of
> "access" is the problem.
>
> Ricky
>
> On Jul 23, 2008, at 11:15 AM, Stéphane Ducasse wrote:
>
>> Hi ricky
>>
>> do you arrive to describe a bit better your problem?
>> Reducing it so that we know if the problem comes from the importer
>> or
>> the exporter.
>>
>> Stef
>>
>> On Jul 21, 2008, at 8:40 PM, Richard Wettel wrote:
>>
>>> Hi,
>>>
>>> I stumble (again) into the same problem.
>>> When importing from an MSE file, I get a MNU exception for
>>> #accessedByList on the FAMIXNamespace UNKNOWN_NAMESPACE.
>>>
>>> Is this something you are aware of?
>>>
>>> I run on top of the latest MooseDevelopment (loaded Moose Config).
>>>
>>> Thanks,
>>> Ricky
>>> _______________________________________________
>>> 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
>
>
> _______________________________________________
> 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
9:37 a.m.
New subject: cyclomatic complexity
Hi all,
I would like to calculate the cyclomatic complexity of a method.
Is there any method in moose which can do that ? or that I can use to
do that ?
Thanks
Jannick
9:51 a.m.
New subject: cyclomatic complexity
Hi,
The method is called #cyclomaticComplexity :).
If you want to compute it for Smalltalk methods, please load the
latest version of MooseDevelopment.
Cheers,
Doru
On Jul 24, 2008, at 9:37 AM, Menanteau Jannick wrote:
Hi all,
I would like to calculate the cyclomatic complexity of a method.
Is there any method in moose which can do that ? or that I can use to
do that ?
Thanks
Jannick
_______________________________________________
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
"Yesterday is a fact.
Tomorrow is a possibility.
Today is a challenge."
9:52 a.m.
Hi,
The problem was that there were accesses to a namespace, and namespace
did not have accessedByList. So, I just pushed the accessors from
FAMIXClass to AbstractScopable.
Cheers,
Doru
On Jul 23, 2008, at 8:53 PM, Stéphane Ducasse wrote:
doru what was the problem in a nutshell?
Stef
On Jul 23, 2008, at 3:18 PM, Richard Wettel wrote:
> Hi all,
>
> The problem arose when referencing a namespace.
> Doru just fixed this problem in version 3.2.113 of MooseDevelopment.
> Thanks, Doru!
>
> Cheers,
> Ricky
>
> On Jul 23, 2008, at 12:21 PM, Richard Wettel wrote:
>
>> Hi Stef,
>>
>> When I do the import, it does the file reading and importing X
>> elements phases, and during the "importing attributes and
>> associations" it throws a Message not understood: #accessedByLists
>> on
>> an instance of FAMIXNamespace (#UNKNOWN_NAMESPACE). The problem
>> seems
>> to be that #accessedByLists is defined in
>> FAMIXAbstractStructuralEntity and FAMIXNamespace is not a subclass
>> of
>> it, but of FAMIXAbstractScopable. Maybe the meta-definition of
>> "access" is the problem.
>>
>> Ricky
>>
>> On Jul 23, 2008, at 11:15 AM, Stéphane Ducasse wrote:
>>
>>> Hi ricky
>>>
>>> do you arrive to describe a bit better your problem?
>>> Reducing it so that we know if the problem comes from the importer
>>> or
>>> the exporter.
>>>
>>> Stef
>>>
>>> On Jul 21, 2008, at 8:40 PM, Richard Wettel wrote:
>>>
>>>> Hi,
>>>>
>>>> I stumble (again) into the same problem.
>>>> When importing from an MSE file, I get a MNU exception for
>>>> #accessedByList on the FAMIXNamespace UNKNOWN_NAMESPACE.
>>>>
>>>> Is this something you are aware of?
>>>>
>>>> I run on top of the latest MooseDevelopment (loaded Moose Config).
>>>>
>>>> Thanks,
>>>> Ricky
>>>> _______________________________________________
>>>> 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
>>
>>
>> _______________________________________________
>> 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
>
_______________________________________________
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
"Yesterday is a fact.
Tomorrow is a possibility.
Today is a challenge."
5:54 p.m.
New subject: Unitary Test with Moose don't work
Hi all,
I would like to make unitary test for several Moose methods.
In this context, I don't use the Moose interface.
I've done this in a method :
model := MooseModel new name: 'model'.
importer := NameSpaceImporter new importingContext:
(NameSpaceImporter new importingContext mergeClassAndMetaclass).
importer model: model; add: Pack1; run.
i := (model entityNamed:#'ModelForQualixoTest') definedClasses .
l := (model entityNamed:#'Root::Smalltalk::Pack1::Class1Pack1')
fanOut.
k := (model entityNamed:#'Root::Smalltalk::Pack1::Class2Pack1')
fanOut.
Class1Pack1 create new object from Class2Pack1.
fanOut for Class1Pack1 must be 1.
The result waited is :
i = OrderedCollection --> ok
l = 1 --> it returns 0
k = 0 --> ok
In Moose interface, the result is good.
I don't know what is the problem :(
Thanks for helping
10:51 p.m.
New subject: Unitary Test with Moose don't work
Hi,
It is easier to answer if we can take a look at the actual code. Where
can I load it from?
Cheers,
Doru
On Jul 24, 2008, at 5:54 PM, Menanteau Jannick wrote:
Hi all,
I would like to make unitary test for several Moose methods.
In this context, I don't use the Moose interface.
I've done this in a method :
model := MooseModel new name: 'model'.
importer := NameSpaceImporter new importingContext:
(NameSpaceImporter new importingContext mergeClassAndMetaclass).
importer model: model; add: Pack1; run.
i := (model entityNamed:#'ModelForQualixoTest') definedClasses .
l := (model entityNamed:#'Root::Smalltalk::Pack1::Class1Pack1')
fanOut.
k := (model entityNamed:#'Root::Smalltalk::Pack1::Class2Pack1')
fanOut.
Class1Pack1 create new object from Class2Pack1.
fanOut for Class1Pack1 must be 1.
The result waited is :
i = OrderedCollection --> ok
l = 1 --> it returns 0
k = 0 --> ok
In Moose interface, the result is good.
I don't know what is the problem :(
Thanks for helping
_______________________________________________
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
"Beauty is where we see it."
9:32 a.m.
New subject: Unitary Test with Moose don't work
Hi,
I've not published my code for the moment.
My code is : (for testing)
---
| model l importer i r d |
model := MooseModel new name: 'model'.
importer := NameSpaceImporter new importingContext:
(NameSpaceImporter new importingContext mergeClassAndMetaclass).
importer model: model; add: Smalltalk.Pack1; run.
i := (model entityNamed:#'ModelForQualixoTest') definedClasses .
l := (model entityNamed:#'Root::Smalltalk::Pack1::Class1Pack1')
invokedClasses.
d := (model entityNamed:#'Root::Smalltalk::Pack1::Class2Pack1')
invokingClasses.
r := (model entityNamed:#'Root::Smalltalk::Pack1::Class3Pack1')
invokingClasses.
---
Results are :
i = Set (a SCG.Moose.FAMIXClass #'Root::Smalltalk::Pack1::Class1Pack1'
a SCG.Moose.FAMIXClass #'Root::Smalltalk::Pack1::Class4Pack1' a
SCG.Moose.FAMIXClass #'Root::Smalltalk::Pack1::Class3Pack1' a
SCG.Moose.FAMIXClass #'Root::Smalltalk::Pack1::Class2Pack1')
l = OrderedCollection (a SCG.Moose.FAMIXClass
#'Root::Smalltalk::Pack1::Class4Pack1')
d = OrderedCollection (a SCG.Moose.FAMIXClass
#'Root::Smalltalk::Pack1::Class1Pack1')
r = OrderedCollection (a SCG.Moose.FAMIXClass
#'Root::Smalltalk::Pack1::Class1Pack1')
---
It's not logical : Class2Pack1 and Class3Pack1 are invoked by
Class1Pack1 (variable d and r) whereas L show that Class1Pack1 invokes
Class4Pack1.
For information, in Class1Pack1, there is just a "new" on the three
others classes.
I also point out that the result is good in Moose.
Have I do an error in declaration of "importer" ?
Thanks for your help
Le 24 juil. 08 à 22:51, Tudor Girba a écrit :
Hi,
It is easier to answer if we can take a look at the actual code. Where
can I load it from?
Cheers,
Doru
On Jul 24, 2008, at 5:54 PM, Menanteau Jannick wrote:
> Hi all,
>
> I would like to make unitary test for several Moose methods.
> In this context, I don't use the Moose interface.
>
> I've done this in a method :
> model := MooseModel new name: 'model'.
> importer := NameSpaceImporter new importingContext:
> (NameSpaceImporter new importingContext mergeClassAndMetaclass).
> importer model: model; add: Pack1; run.
> i := (model entityNamed:#'ModelForQualixoTest') definedClasses .
> l := (model entityNamed:#'Root::Smalltalk::Pack1::Class1Pack1')
> fanOut.
> k := (model entityNamed:#'Root::Smalltalk::Pack1::Class2Pack1')
> fanOut.
>
> Class1Pack1 create new object from Class2Pack1.
> fanOut for Class1Pack1 must be 1.
>
> The result waited is :
> i = OrderedCollection --> ok
> l = 1 --> it returns 0
> k = 0 --> ok
>
> In Moose interface, the result is good.
> I don't know what is the problem :(
>
> Thanks for helping
> _______________________________________________
> 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
"Beauty is where we see it."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
5360
days inactive
5364
days old
10 comments
4 participants
participants (4)
-
Menanteau Jannick -
Richard Wettel -
Stéphane Ducasse -
Tudor Girba