[Mono-dev] corcompare - refactored to use Mono.Cecil instead of reflection

"Andrés G. Aragoneses [ knocte ]" knocte at gmail.com
Thu Dec 21 03:55:00 EST 2006

atsushi eno escribió:
> I'm not a maintainer of corcompare (especially considering that I
> don't touch the class status pages), but anyways - adding further
> dependency on prebuilt managed assembly does not sound a good idea
> to me especially when it becomes part of the build.
> I think you could keep this one as a different tool, probably
> outside mcs tree. We haven't touched corcompare stuff very frequently,
> so having two sources won't be so messy. (I have similar tree in
> olive, but almost no problem).

What about using only stable versions of these kind of tools in the case 
we are using one that is built in the mono tree? This could prevent the 
malfunction in case of bugs in mono tree.

Or perhaps I didn't understand you properly and missed the point here...?


	Andrés	[ knocte ]


More information about the Mono-devel-list mailing list