Guess how I found that out...
time to read 1 min | 11 words
Arrgh!
Ayende @ Rahien
Ayende @ Rahien
Hi!
My name is Oren Eini
Founder of Hibernating Rhinos LTD and RavenDB.
You can reach me by email or phone:
My name is Oren Eini
Founder of Hibernating Rhinos LTD and RavenDB.
You can reach me by email or phone:
+972 52-548-6969
FUTURE POSTS
- RavenDB 4.0 nightly builds are now available - about one hour from now
- Writing SSL Proxy: Part I, routing - about one day from now
- Writing SSL Proxy: Part II, delegating authentication - 2 days from now
- 0.1x or 10x, time matters - 3 days from now
- RavenDB 4.0 Unsung Heroes: Map/reduce - 4 days from now
And 2 more posts are pending...
There are posts all the way to Oct 03, 2017
RECENT SERIES
-
RavenDB 4.0 Unsung Heroes
(4):
22 Sep 2017 - Field compression -
RavenDB 4.0
(13):
11 Sep 2017 - Support options -
Optimizing select projections
(5):
01 Sep 2017 - Part IV–Understand, don’t do -
Optimizing JavaScript and solving the halting problem
(2):
18 Aug 2017 - Part II
RECENT COMMENTS
-
By Oren Eini on RavenDB 4.0 Unsung Heroes: Field compression
-
By Rodrigo Zechin on RavenDB 4.0 Unsung Heroes: Field compression
-
By Ian Yates on Leaning on the compiler
-
By Oren Eini on Leaning on the compiler
-
By HdS on Leaning on the compiler
Syndication
| Main feed |
|
| Comments feed | |
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