r181967 - Start a page tracking which C++ defect reports have been implemented in Clang.

Douglas Gregor dgregor at apple.com
Thu May 16 17:39:47 PDT 2013


On May 15, 2013, at 8:13 PM, Richard Smith <richard at metafoo.co.uk> wrote:

> On Wed, May 15, 2013 at 8:02 PM, Douglas Gregor <dgregor at apple.com> wrote:
>> 
>> 
>> Sent from my iPhone
>> 
>> On May 15, 2013, at 6:23 PM, Richard Smith <richard-llvm at metafoo.co.uk> wrote:
>> 
>> > Author: rsmith
>> > Date: Wed May 15 20:23:30 2013
>> > New Revision: 181967
>> >
>> > URL: http://llvm.org/viewvc/llvm-project?rev=181967&view=rev
>> > Log:
>> > Start a page tracking which C++ defect reports have been implemented in Clang.
>> > The page is generated from a text file listing DR numbers and implementation
>> > status, plus a copy of the cwg_index.html from the WG21 website. Recipe:
>> >
>> >  $ wget http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_index.html
>> >  $ ./make_cxx_dr_status >! cxx_dr_status.html
>> >
>> > The intent here is to go through all the DRs, add tests for each one, then mark
>> > them as done once such tests are committed and passing. I've not linked to this
>> > page from anywhere, since it doesn't contain any useful information yet.
>> 
>> Wow. This is ambitious. I presume we'll have some standard file names and locations for the tests, so at least the bookkeeping will be automated?
> 
> I was intending to have a standard place to put the tests (maybe in test/CXX/DR/, and several DRs per test file). As for the bookkeeping, the script currently generates the table from a file with contents like:
> 
> 1 no
> 3 na
> 4 3.3
> 5 yes
> 7 no
> 8 dup 45
> ...
> 
> which shouldn't be too hard to keep up-to-date as we add tests, but putting markers into the test files themselves would work for me too.

It's not hard, but it's easily forgotten. A trivial bit of tooling eliminates the potential for these to get out of sync. 

I don't insist, though. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20130516/d15037a4/attachment.html>


More information about the cfe-commits mailing list