===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.7/changes.html,v
retrieving revision 1.59
@@ -230,10 +230,11 @@
}
</pre></blockquote></li>
- <li>G++ now accepts the <tt>-std=c++11</tt>, <tt>-std=gnu++11</tt>,
- and <tt>-Wc++11-compat</tt> options, which are equivalent
- to <tt>-std=c++0x</tt>, <tt>-std=gnu++0x</tt>,
- and <tt>-Wc++0x-compat</tt>, respectively.</li>
+ <li>G++ now accepts the <code>-std=c++11</code>,
+ <code>-std=gnu++11</code>, and <code>-Wc++11-compat</code> options,
+ which are equivalent to <code>-std=c++0x</code>,
+ <code>-std=gnu++0x</code>, and <code>-Wc++0x-compat</code>,
+ respectively.</li>
<li>G++ now implements <a href="cxx0x_status.html">C++11</a> extended friend syntax:
<blockquote><pre>
@@ -301,10 +302,11 @@
....
const int &x = f(1);
const int &y = f(2);</pre></blockquote>
-Here, x refers to the temporary allocated to hold the <tt>1</tt> argument,
-which only lives until the end of the initialization; it immediately
-becomes a dangling reference. So the next statement re-uses the stack slot
-to hold the <tt>2</tt> argument, and users of x get that value instead.
+Here, <code>x</code> refers to the temporary allocated to hold the
+<code>1</code> argument, which only lives until the end of the
+initialization; it immediately becomes a dangling reference. So the
+next statement re-uses the stack slot to hold the <code>2</code>
+argument, and users of <code>x</code> get that value instead.
<p>Note that this should not cause any change of behavior for temporaries
of types with non-trivial destructors, as they are already destroyed at end