On 05/12/2013 09:07, Richard Smith wrote:
On Thu, Dec 5, 2013 at 1:01 AM, Alp Toker <[email protected] <mailto:[email protected]>> wrote:On 05/12/2013 08:43, Richard Smith wrote:On Thu, Dec 5, 2013 at 12:23 AM, Alp Toker <[email protected] <mailto:[email protected]>> wrote: Hi Richard, Think it'd make sense to reverse the order of the status page to put newer standards at the top? Right now you have to do a lot of scrolling to get to anything interesting. Search engines also seem to be focusing on C++98 for the search results summary. Yes, the page is definitely getting unwieldy. Perhaps adding a table of contents at the top of the page would help more than reordering the sections? I would guess people are hitting this page for C++11 as much as they are for C++14.Well, I'd go for new features on the top based on the assumption that someone looking for C++11 is still going to find the C++14 status more informative than paging through historic standards.I have a mild preference for chronological order if we can solve the usability problems another way, but no strong objection if you think reverse chronological order is more useful to people.Also, the first thing searching turned up searching for "clang c++ status" is:/Clang/currently implements all of the ISO/C++/1998 standardOuch :-)Yep, that's really not what we want to turn up there. I think we could get a lot of mileage by replacing the introductory text here with something saying "Clang implements all of C++98, C++11, and the draft C++1y standard", with the standard names linking to the relevant sections. Do you want to have a go at improving this page? If not, I'll have a look, but probably not for a few days.
OK, I'll tune the preamble and add a simple TOC. Should address the main points without a full re-ordering.
Taking on board what Chandler said as well and agree that chrono order has its advantages, like not showing a wall of red / incomplete features at first glance.
Alp.
A quick and dirty one-line TOC would still be useful after switching to blog-order though, agreed. Alp.Alp. On 05/12/2013 07:52, Richard Smith wrote: Author: rsmith Date: Thu Dec 5 01:52:05 2013 New Revision: 196482 URL: http://llvm.org/viewvc/llvm-project?rev=196482&view=rev Log: Update C++ status from 'SVN' to 'Clang 3.4' in preparation for release. Leave boxes yellow until we release, though. Modified: cfe/trunk/www/cxx_status.html Modified: cfe/trunk/www/cxx_status.html URL: http://llvm.org/viewvc/llvm-project/cfe/trunk/www/cxx_status.html?rev=196482&r1=196481&r2=196482&view=diff ============================================================================== --- cfe/trunk/www/cxx_status.html (original) +++ cfe/trunk/www/cxx_status.html Thu Dec 5 01:52:05 2013 @@ -417,7 +417,7 @@ table describes the Clang version in whi <tr> <td>Tweak to certain C++ contextual conversions</td> <td><a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2012/n3323.pdf">N3323</a></td> - <td class="svn" align="center">SVN</td> + <td class="svn" align="center">Clang 3.4</td> </tr> <tr> <td>Binary literals</td> @@ -431,27 +431,27 @@ table describes the Clang version in whi </tr> <tr> <td>Return type deduction for normal functions</td> - <td class="svn" align="center">SVN</td> + <td class="svn" align="center">Clang 3.4</td> </tr> <tr> <td>Initialized lambda captures</td> <td><a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3648.html">N3648</a></td> - <td class="svn" align="center">SVN</td> + <td class="svn" align="center">Clang 3.4</td> </tr> <tr> <td>Generic lambdas</td> <td><a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3649.html">N3649</a></td> - <td class="svn" align="center">SVN</td> + <td class="svn" align="center">Clang 3.4</td> </tr> <tr> <td>Variable templates</td> <td><a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3651.pdf">N3651</a></td> - <td class="svn" align="center">SVN</td> + <td class="svn" align="center">Clang 3.4</td> </tr> <tr> <td>Relaxing requirements on constexpr functions</td> <td><a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3652.html">N3652</a></td> - <td class="svn" align="center">SVN</td> + <td class="svn" align="center">Clang 3.4</td> </tr> <tr> <td>Member initializers and aggregates</td> @@ -461,22 +461,22 @@ table describes the Clang version in whi <tr> <td>Clarifying memory allocation</td> <td><a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3664.html">N3664</a></td> - <td class="svn" align="center">SVN</td> + <td class="svn" align="center">Clang 3.4</td> </tr> <tr> <td><tt>[[deprecated]]</tt> attribute</td> <td><a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3760.html">N3760</a></td> - <td class="svn" align="center">SVN</td> + <td class="svn" align="center">Clang 3.4</td> </tr> <tr> <td>Single quotation mark as digit separator</td> <td><a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3781.pdf">N3781</a></td> - <td class="svn" align="center">SVN</td> + <td class="svn" align="center">Clang 3.4</td> </tr> <tr> <td>C++ Sized Deallocation</td> <td><a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3778.html">N3778</a></td> - <td class="svn" align="center">SVN</td> + <td class="svn" align="center">Clang 3.4</td> </tr> </table> @@ -507,7 +507,7 @@ Clang version they became available:</p> <tr> <td>SD-6: SG10 feature test recommendations</td> <td><a href="http://isocpp.org/std/standing-documents/sd-6-sg10-feature-test-recommendations">SD-6</a></td> - <td class="svn" align="center">SVN (<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3745">N3745</a>)</td> + <td class="svn" align="center">Clang 3.4 (<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3745">N3745</a>)</td> </tr> <tr> <td>[DRAFT TS] Array extensions (arrays of runtime bound)</td> _______________________________________________ cfe-commits mailing list [email protected] <mailto:[email protected]> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits-- http://www.nuanti.comthe browser experts-- http://www.nuanti.comthe browser experts
-- http://www.nuanti.com the browser experts _______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
