26 Mar
2014
26 Mar
'14
11:45 a.m.
thanks for pointing that
but don't be too harsh on me, I am only a poor old researcher doing what
he can
that was evolving the idea as I develop the solution, really difficult
I am trying to find time to put my ideas in a paper to formalize everything
and then clean everything
any help is welcome :-)
nicolas
On 26/03/2014 11:12, Yuriy Tymchuk wrote:
On 26 Mar 2014, at 11:01, Nicolas Anquetil <nicolas.anquetil(a)inria.fr
<mailto:nicolas.anquetil@inria.fr>> wrote:
I worked on the generic resolution mechanisms
I made some progress and am trying now to formalize what I learned
and did in a coherent framework
I've seen that :) There is a method called #initScope
in FAMIXContainerEntity. It's overridden
in FAMIXType, FAMIXBehaviouralEntity and FAMIXScopingEntity. All 4
methods are identical :). I think that I will help with this staff. I
think that FAST deserves a good future.
Now the thing is that maybe we should make some general scoping
package and then include it separately in FAMIX and in FAST. Because
not FAST in hacking FAMIX for scopes.
Uko
nicolas
On 25/03/2014 08:58, Yuriy Tymchuk wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Is anyone working on FAST now?
Uko
On 21 Mar 2014, at 19:05, Nicolas Anquetil
<Nicolas.Anquetil(a)inria.fr <mailto:Nicolas.Anquetil@inria.fr>> wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Well to do code critics, you would need to have some representation
of the source code in Famix.
Something like a Famix AST.
hummmm ....
somehow this reminds me of something ...
;-)
For those that could not follow, I am hinting here at FAST
(FAMIX-AST) a project that started with FAST-pharo implemented by
no other than Yuriy Tymchuk.
But seriously, I think that FAMIX is a bit high level to have many
code critics rules.
Andre had implemented some of the rules of smalllint on Famix using
arki, but there are many statement level details that are missing
to go very far.
So I come back to my first answer, the solution seems to be FAST
nicolas
On 21/03/2014 16:45, Yuriy Tymchuk wrote:
> Hi Chris.
>
> The idea is a framework for defining and handling rules. For now
> on I want to try to implement something that works on FAMIX
> because it's a well defined model which already has a lot of
> metrics implemented. We will see how it will work in future. I'd
> like to have it in Pharo on the same importance level as SUnit.
>
> Cheers.
> Uko
>
> On 21 Mar 2014, at 15:31, Chris Cunningham
> <cunningham.cb(a)gmail.com <mailto:cunningham.cb@gmail.com>> wrote:
>
>> Cross-language code smells, or a framework to build a language
>> specific code critic? I don't have either one, but the idea of a
>> cross-languange code smell is interesting to me.
>>
>> -cbc
>>
>>
>> On Fri, Mar 21, 2014 at 7:20 AM, Yuriy Tymchuk
>> <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>> wrote:
>>
>> No. I want to work with rules that can find common code
>> smells, and so I wander if something similar is implemented
>> already.
>>
>> Uko
>>
>> Sent from my iPhone
>>
>> On 21 Mar 2014, at 15:15, Tudor Girba <tudor(a)tudorgirba.com
>> <mailto:tudor@tudorgirba.com>> wrote:
>>
>>> What do you mean exactly?
>>>
>>> Doru
>>>
>>>
>>> On Fri, Mar 21, 2014 at 2:55 PM, Yuriy Tymchuk
>>> <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>> wrote:
>>>
>>> Hi everyone.
>>>
>>> Can someone tell me if there was any implementation of
>>> code critics-like framework on top of FAMIX?
>>>
>>> Regards.
>>> Yuriy
>>> _______________________________________________
>>> Moose-dev mailing list
>>> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>
>>>
>>>
>>>
>>> --
>>> www.tudorgirba.com <http://www.tudorgirba.com/>
>>>
>>> "Every thing has its own flow"
>>> _______________________________________________
>>> Moose-dev mailing list
>>> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch>
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@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 <mailto:Moose-dev@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