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  <jist...@redhat.com>

        * htdocs/gcc-4.7/porting_to.html: Use straight quotes in code
        examples, and expand a <code> wrapper around the operator term.

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>

Reply via email to