Fixing source files = adding MIT headers?
I can do it over the weekend.
On Fri, Oct 14, 2011 at 1:47 PM, Alexandre Bergel
<alexandre.bergel(a)me.com>wrote;wrote:
There is no problem to turn the code into MIT.
Usman, do you have time to fix the source files? I could do it else.
Alexandre
On 10 Oct 2011, at 11:02, Usman Bhatti wrote:
On Mon, Oct 10, 2011 at 3:03 PM, Alexandre Bergel
<
alexandre.bergel(a)me.com> wrote:
I like the idea, but we should be cautious. As
you can see, the source
are Microsoft copyrighted. Peli and I did this as a proof
of concept and as
an opportunity to code together. We did not talk about distributing it.
Ok let me know, and I'll remove the code from the svn or make it private,
if
possible.
I will talk to him about that.
Alexandre
On 9 Oct 2011, at 07:55, Usman Bhatti wrote:
> I added the project here with some related info from the mail on the
list.
>
>
http://code.google.com/p/moosecciextractor/
>
> If someone needs access, send me a mail.
>
>
> On Thu, Sep 29, 2011 at 10:00 PM, Usman Bhatti <usman.bhatti(a)gmail.com>
wrote:
> ok i'll upload it somewhere ...
>
>
> On Thu, Sep 29, 2011 at 10:54 AM, Stéphane Ducasse <
stephane.ducasse(a)inria.fr> wrote:
> Could we add all the code in a svn
somewhere?
>
> Stef
>
> On Sep 28, 2011, at 4:42 PM, Usman Bhatti wrote:
>
> > tx
> >
> > On Wed, Sep 28, 2011 at 2:42 PM, Alexandre Bergel <
alexandre.bergel(a)me.com> wrote:
> > Apparently, gmail does not like my
email. I put it on dropbox
> >
http://dl.dropbox.com/u/31543901/petomse.zip
> >
> > Cheers,
> > Alexandre
> >
> >
> > On 28 Sep 2011, at 09:26, Alexandre Bergel wrote:
> >
> > > I just sent the code to the mailing list.
> > > I will send it privately if it is not accepted by the list.
> > >
> > > Cheers,
> > > Alexandre
> > >
> > >
> > > On 28 Sep 2011, at 08:31, Usman Bhatti wrote:
> > >
> > >> Alex,
> > >>
> > >> If you could share the code that you create with MS guys, it would
be great ... just to compare the two implementations and learn a few lessons
:-)
> > >>
> > >> thanx
> > >>
> > >> Usman
> > >>
> > >> On Wed, Sep 28, 2011 at 1:30 PM, Usman Bhatti <
usman.bhatti(a)gmail.com> wrote:
> > >> On Wed, Sep 28, 2011 at 8:04
AM, Stéphane Ducasse <
stephane.ducasse(a)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…
> > >> + 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(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
>>>
>>> --
>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>>> 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
>>
>>
>> _______________________________________________
>> 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
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> 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
_______________________________________________
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
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
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
_______________________________________________
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