On 10/27/2013 05:17 AM, Paolo Carlini wrote:
On 10/22/2013 02:28 PM, Ed Smith-Rowland wrote:
I think this is pretty easy - gnu::deprecated has the same semantics.
Since we decided to have this now, we should also update the docs, thus htdocs/projects/cxx1y.html (which normally would link htdocs/gcc-4.9/changes.html, thus a line or so there too).

Thanks!
Paolo.

My last email had a bad patch.

Try this one.

OK?

Index: htdocs/projects/cxx1y.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/cxx1y.html,v
retrieving revision 1.8
diff -r1.8 cxx1y.html
113,114c113,115
<       <td><a href="http://isocpp.org/files/papers/n3760.htm";>N3760</a></td>
<       <td class="unsupported" align="center">No</td>
---
>       <td><a 
> href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3760.html";>N3760</a></td>
>       <td class="supported" align="center">
>         <a href="../gcc-4.9/changes.html#cxx">4.9</a> (N3797)</td>
118,119c119,121
<       <td><a href="http://isocpp.org/files/papers/N3781.pdf";>N3781</a></td>
<       <td class="unsupported" align="center">No</td>
---
>       <td><a 
> href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3781.pdf";>N3781</a></td>
>       <td class="supported" align="center">
>         <a href="../gcc-4.9/changes.html#cxx">4.9</a> (N3797)</td>
Index: htdocs/gcc-4.9/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.9/changes.html,v
retrieving revision 1.32
diff -r1.32 changes.html
150a151,182
>     G++ supports the <a href="../projects/cxx1y.html">C++1y</a> [[deprecated]]
>     attribute modulo bugs in the underying [[gnu::deprecated]] attribute.  
> Classes
>     and functions can be marked deprecated and 
> <blockquote><pre>
> </pre></blockquote>
>   <li>
> class A {};
> int bar(int n)
> { return 42 + n - 1; }
> #if __cplusplus > 201103:
> class [[deprecated("A is deprecated in C++14; Use B instead")]] A;
> [[deprecated("bar is unsafe; use foo() instead")]]
> int bar(int n);
> 
> int foo(int n) { return 42 + n; }
> class B {};
> #endif
>   </li>
>   <li>
>     G++ supports <a href="../projects/cxx1y.html">C++1y</a> digit separators.
>     Long numeric literals can be subdivided with a single quote ' to enhance 
> readability:
> <blockquote><pre>
>   int i = 1048576;
>   int j = 1'048'576;
>   int k = 0x10'0000;
>   int m = 0'004'000'000;
>   int n = 0b0001'0000'0000'0000'0000'0000;
> 
>   double x = 1.602'176'565e-19;
>   double y = 1.602'176'565e-1'9;
> </pre></blockquote>
>   </li>
158a191,213
>     <li><a 
> href="http://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html#status.iso.2014";>
>        Improved experimental support for the upcoming ISO C++ standard, 
> C++14</a>,
>        including:
>       <ul>
>         <li> fixing <code>constexpr</code> member functions without 
> <code>const</code>; </li>
>         <li> implementation of the <code>exchange()</code> utility function; 
> </li>
>         <li> addressing tuples by type; </li>
>         <li> implemention of <code>make_unique</code>; </li>
>         <li> making <code>std::result_of</code> SFINAE-friendly; </li>
>         <li> adding <code>operator()</code> to 
> <code>integral_constant</code>; </li>
>         <li> adding user-defined literals for standard library types
>              </code>string</code>, </code>chrono</code>, and 
> </code>complex</code>; </li>
>         <li> adding two range overloads to non-modifying sequence oprations; 
> </li>
>         <li> adding IO manipulators for quoted strings; </li>
>         <li> adding <code>constexpr</code> members to utilities, 
> <code>complex</code>,
>              <code>chrono</code>, and some containers; </li>
>         <li> adding compile-time <code>integer_sequence</code>s; </li>
>         <li> adding cleaner transformation traits; </li>
>         <li> adding a class for <code>optional</code> types; </li>
>         <li> making <code>functional</code>s operator functors easier to use 
> and
>              more generic; </li>
>       </ul>
>     </li>

Reply via email to