Patchwork [wwwdocs] Fix quoting in gcc-4.7/porting_to.html

login
register
mail settings
Submitter Josh Stone
Date Jan. 27, 2012, 12:11 a.m.
Message ID <201201270011.q0R0BEli025658@int-mx09.intmail.prod.int.phx2.redhat.com>
Download mbox | patch
Permalink /patch/138088/
State New
Headers show

Comments

Josh Stone - Jan. 27, 2012, 12:11 a.m.
Hi,

I noticed that the porting example for c++11 user-defined literals is
using "smart" double quotes, when code should have straight quotes.
There's also an operator term that should be in the nearby <code> block.

Thanks,
Josh


2012-01-26  Josh Stone  <jistone@redhat.com>

        * htdocs/gcc-4.7/porting_to.html: Use straight quotes in code
        examples, and expand a <code> wrapper around the operator term.
Gerald Pfeifer - Jan. 27, 2012, 1:06 a.m.
On Thu, 26 Jan 2012, Josh Stone wrote:
> I noticed that the porting example for c++11 user-defined literals is
> using "smart" double quotes, when code should have straight quotes.
> There's also an operator term that should be in the nearby <code> block.

Good catches, both of them, Josh!  And thanks for even providing a
patch which I went ahead and committed right away.

Gerald

Patch

Index: htdocs/gcc-4.7/porting_to.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.7/porting_to.html,v
retrieving revision 1.6
diff -u -p -r1.6 porting_to.html
--- htdocs/gcc-4.7/porting_to.html	12 Jan 2012 21:15:51 -0000	1.6
+++ htdocs/gcc-4.7/porting_to.html	26 Jan 2012 23:52:21 -0000
@@ -215,19 +215,19 @@  valid ISO C++03 code
 </p>
 
 <pre>
-const char *p = &ldquo;foobar&rdquo;__TIME__;
+const char *p = &quot;foobar&quot;__TIME__;
 </pre>
 
 <p>In C++03, the <code>__TIME__</code> macro expands to some string
 literal and is concatenated with the other one.  In
-C++11 <code>__TIME__</code> isn't expanded, instead operator
-&ldquo;&rdquo; <code>__TIME__</code> is being looked up, resulting in the
+C++11 <code>__TIME__</code> isn't expanded, instead <code>operator
+&quot;&quot; __TIME__</code> is being looked up, resulting in the
 following diagnostic:
 </p>
 
 <pre>
  error: unable to find string literal operator
- &lsquo;operator&ldquo;&rdquo; __TIME__&rsquo;
+ &lsquo;operator&quot;&quot; __TIME__&rsquo;
 </pre>
 
 <p>