From: | Greg Stark <stark(at)mit(dot)edu> |
---|---|
To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
Cc: | Tom Browder <tom(dot)browder(at)gmail(dot)com>, Developer discussions <brlcad-devel(at)lists(dot)sourceforge(dot)net>, "dev(at)httpd(dot)apache(dot)org" <dev(at)httpd(dot)apache(dot)org>, perl6-compiler(at)perl(dot)org, openssl-dev(at)openssl(dot)org, postfix-devel(at)postfix(dot)org, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, cyrus-devel(at)lists(dot)andrew(dot)cmu(dot)edu, pcre-dev(at)exim(dot)org, perl5-porters(at)perl(dot)org |
Subject: | Re: Static code checker research worth investigating (Communications of the ACM, 03/2016, Vol. 59, No. 03, p. 99) |
Date: | 2016-03-05 12:59:18 |
Message-ID: | CAM-w4HNfjubOHM5w5UFvMk-m5nj+yHRUvM5XN2--vMc+-MWQQg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Mar 5, 2016 at 12:41 PM, Tomas Vondra
<tomas(dot)vondra(at)2ndquadrant(dot)com> wrote:
> And it was dealt with
Well. Not dealt with yet. I think it's more or less clear how to
tackle it using macros and builtins now but there's a lot of drudgery
work to actually rewrite all the checks. I have the reports from Xi
Wang's tool saved if anyone else wants to take it up. I would say it's
on my TODO list but that's more of an abstract concept than an actual
list.
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2016-03-05 13:03:26 | Re: Static code checker research worth investigating (Communications of the ACM, 03/2016, Vol. 59, No. 03, p. 99) |
Previous Message | Tom Browder | 2016-03-05 12:51:27 | Re: Static code checker research worth investigating (Communications of the ACM, 03/2016, Vol. 59, No. 03, p. 99) |