This patch fixes some code styles caused by bugs of add_new_check.py script.
Details
Diff Detail
Event Timeline
I'm wondering whether should we rename CERT to cert to keep the same with other modules like misc and google.
For adding a new check in CERT module, you need to use the upper name explicitly via python add_new_check.py CERT foo rather than python add_new_check.py cert foo.
Fine by me -- I went with CERT since it's an acronym, but we don't do this for LLVM, so this change makes sense. Thanks!
AFAIU, LLVM is not an acronym anymore ;) (but still an upper-case spelling is the correct one).
Fine by me -- I went with CERT since it's an acronym, but we don't do this for LLVM, so this change makes sense. Thanks!
Hah, good point. ;-) Regardless, I am fine with the namespace being "cert" in code so that it isn't confused with a macro.
Yes, but just the namespaces as you do in this patch (not anything in user documentation, for instance). This patch LG; if you need me to commit on your behalf, I'm happy to do so.
Yes, but just the namespaces as you do in this patch (not anything in user documentation, for instance). This patch LG; if you need me to commit on your behalf, I'm happy to do so.
Done. But My account has no write access to the code repo. Can I commit the patch by myself? If not, I'm happy you can land it on my behalf :)
You can ask Chris Lattner for commit privileges if you would like to commit this yourself (http://llvm.org/docs/DeveloperPolicy.html#obtaining-commit-access). Let me know if you want me to commit instead.