Guess how I found that out... previous: I, too, broke the compiler next: You can checkout, but you can not commit Arrgh! Comments 07/01/2008 04:14 AM by Yitzchok Interesting catch Who has the mistake? 07/01/2008 04:25 AM by Ayende Rahien Both can be argued to be correct. The problem is not that, it is that there is a difference. 07/01/2008 04:41 AM by Chris Patterson So now that the source to the CLR is viewable by the public, how does that impact the mono project and future versions I wonder? 07/01/2008 04:47 AM by Ayende Rahien Same as always, if you look at CLR code, please don't contribute to Mono 07/01/2008 05:36 AM by Simon Mono is correct because it does not use crappy "m_" prefixing for member types. ;) 07/01/2008 05:38 AM by Scott Hanselman Shoot! Now that I've glanced at this post, I can't go fix this bug for you! AARGH! My eyes! ;) 07/01/2008 05:47 AM by josh Maybe you should have put a spoiler warning on this for any mono devs. I wouldn't be surprised if some were among your readers. 07/01/2008 05:49 AM by Ayende Rahien This did not come from the CLR sources. This is a reflector output. Beside, I frankly doubt that anyone will reveal the secret of PROPERTY GETTERS 07/01/2008 05:49 AM by josh @Hanselmen, don't worry the mono team has an official eye bleach for just this sort of situation. 07/01/2008 11:36 AM by Stefan Wenig gotta get one of those: http://www.youtube.com/watch?v=c7vqvdwkvJk&NR=1 07/01/2008 12:00 PM by firefly Good catch :) So what does CheckDisposed() do? throw an exception if the object is disposed? 07/01/2008 12:58 PM by Jarrod M I ran into a few things like this when working with Mainsoft (which uses Mono source to cross compile to java with their compiler). By the way, what do you use to create your diagrams? 07/01/2008 02:04 PM by Ayende Rahien Firefly, Yes 07/01/2008 02:09 PM by Ayende Rahien Jarrod, PowerPoint 07/01/2008 02:30 PM by MIguel de Icaza We only use m_ names when we are forced by something like remoting (which likes to send reflection-based internal field names across the wire). Otherwise we stay away from that horrible practice. Miguel Comments have been closed on this topic.
07/01/2008 04:25 AM by Ayende Rahien Both can be argued to be correct. The problem is not that, it is that there is a difference.
07/01/2008 04:41 AM by Chris Patterson So now that the source to the CLR is viewable by the public, how does that impact the mono project and future versions I wonder?
07/01/2008 04:47 AM by Ayende Rahien Same as always, if you look at CLR code, please don't contribute to Mono
07/01/2008 05:36 AM by Simon Mono is correct because it does not use crappy "m_" prefixing for member types. ;)
07/01/2008 05:38 AM by Scott Hanselman Shoot! Now that I've glanced at this post, I can't go fix this bug for you! AARGH! My eyes! ;)
07/01/2008 05:47 AM by josh Maybe you should have put a spoiler warning on this for any mono devs. I wouldn't be surprised if some were among your readers.
07/01/2008 05:49 AM by Ayende Rahien This did not come from the CLR sources. This is a reflector output. Beside, I frankly doubt that anyone will reveal the secret of PROPERTY GETTERS
07/01/2008 05:49 AM by josh @Hanselmen, don't worry the mono team has an official eye bleach for just this sort of situation.
07/01/2008 11:36 AM by Stefan Wenig gotta get one of those: http://www.youtube.com/watch?v=c7vqvdwkvJk&NR=1
07/01/2008 12:00 PM by firefly Good catch :) So what does CheckDisposed() do? throw an exception if the object is disposed?
07/01/2008 12:58 PM by Jarrod M I ran into a few things like this when working with Mainsoft (which uses Mono source to cross compile to java with their compiler). By the way, what do you use to create your diagrams?
07/01/2008 02:30 PM by MIguel de Icaza We only use m_ names when we are forced by something like remoting (which likes to send reflection-based internal field names across the wire). Otherwise we stay away from that horrible practice. Miguel
Comments
Interesting catch
Who has the mistake?
Both can be argued to be correct.
The problem is not that, it is that there is a difference.
So now that the source to the CLR is viewable by the public, how does that impact the mono project and future versions I wonder?
Same as always, if you look at CLR code, please don't contribute to Mono
Mono is correct because it does not use crappy "m_" prefixing for member types. ;)
Shoot! Now that I've glanced at this post, I can't go fix this bug for you! AARGH! My eyes! ;)
Maybe you should have put a spoiler warning on this for any mono devs. I wouldn't be surprised if some were among your readers.
This did not come from the CLR sources. This is a reflector output.
Beside, I frankly doubt that anyone will reveal the secret of PROPERTY GETTERS
@Hanselmen, don't worry the mono team has an official eye bleach for just this sort of situation.
gotta get one of those: http://www.youtube.com/watch?v=c7vqvdwkvJk&NR=1
Good catch :) So what does CheckDisposed() do? throw an exception if the object is disposed?
I ran into a few things like this when working with Mainsoft (which uses Mono source to cross compile to java with their compiler).
By the way, what do you use to create your diagrams?
Firefly,
Yes
Jarrod,
PowerPoint
We only use m_ names when we are forced by something like remoting (which likes to send reflection-based internal field names across the wire).
Otherwise we stay away from that horrible practice.
Miguel