If memory serves me right, Paolo Molaro wrote: > _If_ the issue is an API issue with Reflection.Emit you'll be affected as > well when you'll implement it, the fact that cscc doesn't use Reflection > doesn't matter one bit. Unless, of course, you implement a different > API. ....... > > like this one).. It looks like Reflection.Emit API isn't as hot as they > > were made up to be ...
(we agreed on that ?). > It looks like this was an issue in pnet, just like the PropertyMap one, <earlier from the thread> > Indeed, it works with the mono runtime, too. > I went and changed mcs to use the typebuilder type as the type of the > fields and it _seems_ to work ok (full bootstrap build of mcs and all </end> (MCS fixed and pnet has bugs) hmm... looks like we agree more than you did with yourself ... :-) there were bugs on either side .... and fixed on both sides as well, when fixing it once would have been enough and hence the term "virtual bug". > so please take the flame bait somewhere else. Huh ? ... I've gone through my mail twice and can't see any flame bait... Aren't you over-reacting a bit ? ... Gopal -- The difference between insanity and genius is measured by success _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
