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

From Tom Browder
Subject Re: Static code checker research worth investigating (Communications of the ACM, 03/2016, Vol. 59, No. 03, p. 99)
Date
Msg-id CAFMGiz_o6AbFF-Mo_8q1AvgQHFyh+Q3XZB9ydUuzsN76FcsoEg@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)  (Greg Stark <stark@mit.edu>)
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 7:03 AM, Greg Stark <stark@mit.edu> wrote:
> On Sat, Mar 5, 2016 at 12:59 PM, Greg Stark <stark@mit.edu> wrote:
>> 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.
>
> [Removing all the other xposted lists -- don't do that!]

Okay, sorry.  I thought since the reply was pg-specific it would cut down noise.

-Tom



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: VS 2015 support in src/tools/msvc
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)