Begin forwarded message:
> From: "Valloud, Andres" <avalloud(a)cincom.com>
> Date: January 24, 2009 10:27:26 AM CEST
> To: "VWNC" <vwnc(a)cs.uiuc.edu>
> Subject: [vwnc] Assistance request
> I am doing some work with short compiled methods, and I would like
> some information from actual application images. The attached
> parcel adds a few methods to CompiledCode in order to make the
> needed observation. The code that performs the measurement is in
> the comments of the parcel. To produce the needed data, load the
> parcel, inspect the result of evaluating the code in the parcel's
> comments, and send me the resulting list of triplets. Thanks in
> PS: note that the measurement will modify many of the compiled
> methods in the image... this should not cause problems because the
> resulting compiled methods are equivalent after the modifications
> are done. However, you may want to ditch the image after the
> triplets are created.
> vwnc mailing list
<MSEProperty: #accesses type: #FAMIX2Access opposite: #accessedIn>
"all variable accesses contained in receiver"
accesses isNil ifTrue: [ accesses := OrderedCollection new ].
what is the equivalence in FAMIX30?
just two lines summary of what we did today.
- Now there is a mooseLoader :)
- instanceSide and classSide now working FAMIX30.
- Added some method to RBVariableNode to support isSuper identification
- Fixed the parsetree metric calculator.
Now we get number of statements and friends on Famix20 and Famix30
- Fixed some tests for importer.
Normally when I'm done with some pending documents I will do fix the
Thursday we organise a Moose sprint.
I thought that it might represent a class reference.
But if you want to represent a class reference with an FAMIXAccess, why not
change the type of the accesses attribute from FAMIXAbstractStructuralEntity
to FAMIXNamedEntity? This would fix the issue. Right?
>Indeed this is correct. We knew this was a hack, and that is why we
>tried to solve this in FAMIX 3.0.
>On Jan 21, 2009, at 10:04 PM, St?phane Ducasse wrote:
>> I do not remember but I guess that
>> the problem is that in famix2 there is no way to express class
>> references (class A refers to class B).
>> so we used that because if in your code you have
>> ^ B zork
>> Now in FAMIX30 this is different.
>> You can have reference between classes.
>> Doru am I correct? I'm dead this evening.
>> On Jan 20, 2009, at 11:27 PM, Adrian DOZSA wrote:
>>> Hi everybody,
>>> Playing around with the FAMIX 2 specs and the LAN model I found
>>> something very strange:
>>> - I found an FAMIXAccess that accesses a FAMIXClass. According to
>>> the FAMIX 2 meta-model and also the annotations from Moose the
>>> accesses attribute of FAMIXAccess should be of type
>>> FAMIXAbstractStructuralEntity. But the FAMIXAccess instance with id
>>> 71 from LAN model accesses a FAMIXClass
>>> (Root::Smalltalk::LAN::LANInterface.initialize() ->
>>> There are other examples too.
>>> How were those accesses build? It is correct?
>>> Adi D.
I'm looking at the moose website and I think we could improve it a bit
by making some categories/facets for the tools section: like core,
utils, importer, visualization, analysis...
Right now if I want to know which languages can be imported in moose,
I have to go in the FAQ section, which is cumbersome.