[cfe-dev] clang-tidy checks for High integrity C++

Piotr Padlewski via cfe-dev cfe-dev at lists.llvm.org
Mon Jan 23 15:34:00 PST 2017


Thanks,
before working on the patch, I would suggest adding a couple of ideas of
checks to bugzilla, so you will be able to gather comments about how hard
it might be and if it make sens.

2017-01-23 23:39 GMT+01:00 Jonathan Coe <jbcoe at me.com>:

>
>
> On 23 January 2017 at 22:13, Piotr Padlewski <piotr.padlewski at gmail.com>
> wrote:
>
>>
>>
>> 2017-01-23 23:07 GMT+01:00 Jonathan Coe via cfe-dev <
>> cfe-dev at lists.llvm.org>:
>>
>>> Would there be any interest in implementing/using clang-tidy checks for
>>> high-integrity C++?
>>>
>>> http://www.programmingresearch.com/coding-standards/high-integrity-cpp/
>>>
>>> This is a set of standard used in some safety-critical systems. Some of
>>> the rules look simple enough to implement as clang-tidy checks.
>>>
>>> Can you share the coding standard that is used there?
>>
>>
>
> I did not see any restrictions on distribution of the PDF I got. Please
> see attached file.
>
>
>> With enough people interested in reviewing patches I can happily make a
>>> start and add a new module to clang-tidy.
>>>
>>> Usually there are a few people reviewing patches quickly. You can always
>> add me to reviewers.
>>
>
> If you're happy to be a reviewer then I'll get started.
>
> Thanks!
>
> Jon
>
>
>>
>> Piotr
>>
>>
>>> Regards,
>>>
>>> Jon
>>>
>>> _______________________________________________
>>> cfe-dev mailing list
>>> cfe-dev at lists.llvm.org
>>> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20170124/d75ad055/attachment.html>


More information about the cfe-dev mailing list