+972 52-548-6969
Guess how I found that out...
time to read 1 min | 11 words
Arrgh!
FUTURE POSTS
- Expertise in the age of AI, or: Matt's Claude'll handle this - about one day from now
- 15+ years of working with coding agents - 6 days from now
- Putting Claude up against our test suite - 8 days from now
- The GPU Is the New Bangalore - 10 days from now
- Learning to code, 1990s vs 2026 - 14 days from now
There are posts all the way to May 05, 2026
RECENT SERIES
-
API Design
(10):
29 Jan 2026 - Don't try to guess -
Recording
(20):
05 Dec 2025 - Build AI that understands your business -
Webinar
(8):
16 Sep 2025 - Building AI Agents in RavenDB -
RavenDB 7.1
(7):
11 Jul 2025 - The Gen AI release -
Production postmorterm
(2):
11 Jun 2025 - The rookie server's untimely promotion
RECENT COMMENTS
-
By Barth Benner on The 'Million AI Monkeys' Hypothesis & Real-World Projects
-
By Oren Eini on A tale of one-off, coding agents and the shortest path to victory
-
By Rustam on A tale of one-off, coding agents and the shortest path to victory
-
By Nicholas Piasecki on Maintainability in the age of coding agents
-
By Oren Eini on Implementing Agentic Reminders in RavenDB
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
Comment preview