Usman

On Wed, Sep 28, 2011 at 1:30 PM, Usman Bhatti <usman.bhatti@gmail.com> wrote:

On Wed, Sep 28, 2011 at 8:04 AM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:

On Sep 27, 2011, at 7:42 PM, Alexandre Bergel wrote:

> Sorry, I missed this email
> We simply extract the class declaration, attributes, methods and their invocations. We also say whether a method is public or not, whether it is abstract.
>
> Nothing about the AST. Quite simple actually. The CCI looks quite expressive.

But I do not understand how you can do invocations without AST analysis?
what is the license of CCI?

CCI and Mono.Cecil (that we use for VerveineSharp) provide libraries to manipulate MSIL (i.e. MS byte code), hence these are competing frameworks... since we are working on the byte code therefore it is not needed to touch AST. Hence, one can go very fast to create static analyzers with these tools.

Licence: Microsoft Public License (Ms-PL)

From here: http://ccimetadata.codeplex.com/license

Comparison of the two frameworks:

http://stackoverflow.com/questions/6727715/cci-vs-mono-cecil-advantages-and-disadvantages

+ Mono. Cecil community is much more vibrant ..

>
> Alexandre
>
>
> On 27 Sep 2011, at 04:49, Stéphane Ducasse wrote:
>
>> alex can you reply?
>>
>> Stef
>>
>> On Sep 23, 2011, at 2:46 PM, Stéphane Ducasse wrote:
>>
>>> what model did you extract?
>>> inside methods?
>>> symbol resolved?
>>> because get package, class and inheritance should be simple.
>>>
>>>
>>> On Sep 23, 2011, at 2:08 PM, Alexandre Bergel wrote:
>>>
>>>> Hi !
>>>>
>>>> Yesterday I spent about 30 minutes with a guy from microsoft to generate .mse from C#. We were able to extract the data and generate the mse. I was happy to have a blueprint complexity after such a short amount of time.
>>>>
>>>> Usman, we use http://ccimetadata.codeplex.com for extracting the data. I can share the code if you wish.
>>>>
>>>> Cheers,
>>>> Alexandre
>>>>
>>>>
>>>> --
>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>>>> Alexandre Bergel http://www.bergel.eu
>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Moose-dev mailing list
>>>> Moose-dev@iam.unibe.ch
>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>
>>>
>>> _______________________________________________
>>> Moose-dev mailing list
>>> Moose-dev@iam.unibe.ch
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev@iam.unibe.ch
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> Moose-dev@iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev