mirror of https://github.com/rust-lang/book
Fix QuotePara
This commit is contained in:
parent
03cd731b27
commit
739c283cf2
|
@ -278,11 +278,17 @@ two states: null or not-null.
|
|||
In his 2009 presentation “Null References: The Billion Dollar Mistake,” Tony
|
||||
Hoare, the inventor of null, has this to say:
|
||||
|
||||
|
||||
Unmatched: QuotePara
|
||||
The problem with null values is that if you try to use a null value as a
|
||||
not-null value, you’ll get an error of some kind. Because this null or not-null
|
||||
property is pervasive, it’s extremely easy to make this kind of error.
|
||||
> I call it my billion-dollar mistake. At that time, I was designing the first
|
||||
comprehensive type system for references in an object-oriented language. My
|
||||
goal was to ensure that all use of references should be absolutely safe, with
|
||||
checking performed automatically by the compiler. But I couldn’t resist the
|
||||
temptation to put in a null reference, simply because it was so easy to
|
||||
implement. This has led to innumerable errors, vulnerabilities, and system
|
||||
crashes, which have probably caused a billion dollars of pain and damage in the
|
||||
last forty years.The problem with null values is that if you try to use a null
|
||||
value as a not-null value, you’ll get an error of some kind. Because this null
|
||||
or not-null property is pervasive, it’s extremely easy to make this kind of
|
||||
error.
|
||||
|
||||
However, the concept that null is trying to express is still a useful one: a
|
||||
null is a value that is currently invalid or absent for some reason.
|
||||
|
|
|
@ -215,7 +215,7 @@
|
|||
<xsl:text> </xsl:text>
|
||||
</xsl:template>
|
||||
|
||||
<xsl:template match="w:p[w:pPr/w:pStyle[@w:val = 'BlockQuote']]">
|
||||
<xsl:template match="w:p[w:pPr/w:pStyle[@w:val = 'BlockQuote' or @w:val = 'QuotePara']]">
|
||||
<xsl:text>> </xsl:text>
|
||||
<xsl:apply-templates select="*" />
|
||||
</xsl:template>
|
||||
|
|
Loading…
Reference in New Issue