Guess how I found that out...
time to read 1 min | 11 words
Arrgh!
Markdown formatting
ESC to close
Markdown turns plain text formatting into fancy HTML formatting.
Phrase Emphasis
*italic* **bold**
_italic_ __bold__
Links
Inline:
An [example](http://url.com/ "Title")
Reference-style labels (titles are optional):
An [example][id]. Then, anywhere
else in the doc, define the link:
[id]: http://example.com/ "Title"
Images
Inline (titles are optional):
Reference-style:
![alt text][id]
[id]: /url/to/img.jpg "Title"
Headers
Setext-style:
Header 1
========
Header 2
--------
atx-style (closing #'s are optional):
# Header 1 #
## Header 2 ##
###### Header 6
Lists
Ordered, without paragraphs:
1. Foo
2. Bar
Unordered, with paragraphs:
* A list item.
With multiple paragraphs.
* Bar
You can nest them:
* Abacus
* answer
* Bubbles
1. bunk
2. bupkis
* BELITTLER
3. burper
* Cunning
Blockquotes
> Email-style angle brackets
> are used for blockquotes.
> > And, they can be nested.
> #### Headers in blockquotes
>
> * You can quote a list.
> * Etc.
Horizontal Rules
Three or more dashes or asterisks:
---
* * *
- - - -
Manual Line Breaks
End a line with two or more spaces:
Roses are red,
Violets are blue.
Fenced Code Blocks
Code blocks delimited by 3 or more backticks or tildas:
```
This is a preformatted
code block
```
Header IDs
Set the id of headings with {#<id>} at end of heading line:
## My Heading {#myheading}
Tables
Fruit |Color
---------|----------
Apples |Red
Pears |Green
Bananas |YellowDefinition Lists
Term 1
: Definition 1
Term 2
: Definition 2Footnotes
Body text with a footnote [^1]
[^1]: Footnote text here
Abbreviations
MDD <- will have title
*[MDD]: MarkdownDeep
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