Re: Static code checker research worth investigating (Communications of the ACM, 03/2016, Vol. 59, No. 03, p. 99) - Mailing list pgsql-hackers

From Greg Stark
Subject Re: Static code checker research worth investigating (Communications of the ACM, 03/2016, Vol. 59, No. 03, p. 99)
Date
Msg-id CAM-w4HNfjubOHM5w5UFvMk-m5nj+yHRUvM5XN2--vMc+-MWQQg@mail.gmail.com
Whole thread Raw
In response to Re: Static code checker research worth investigating (Communications of the ACM, 03/2016, Vol. 59, No. 03, p. 99)  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
Responses Re: Static code checker research worth investigating (Communications of the ACM, 03/2016, Vol. 59, No. 03, p. 99)
List pgsql-hackers
On Sat, Mar 5, 2016 at 12:41 PM, Tomas Vondra
<tomas.vondra@2ndquadrant.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



pgsql-hackers by date:

Previous
From: Tom Browder
Date:
Subject: Re: Static code checker research worth investigating (Communications of the ACM, 03/2016, Vol. 59, No. 03, p. 99)
Next
From: Greg Stark
Date:
Subject: Re: Static code checker research worth investigating (Communications of the ACM, 03/2016, Vol. 59, No. 03, p. 99)