[HACKERS] Re: Static code checker research worth investigating (Communications of the ACM, 03/2016, Vol. 59, No. 03, p. 99)

2016-03-05 Thread Greg Stark
On Sat, Mar 5, 2016 at 2:35 PM, Tom Browder wrote: >> [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. I'm sorry I was unclear. I meant, I was removing all the others from my reply and was saying not t

[HACKERS] Re: Static code checker research worth investigating (Communications of the ACM, 03/2016, Vol. 59, No. 03, p. 99)

2016-03-05 Thread Tom Browder
On Sat, Mar 5, 2016 at 7:03 AM, Greg Stark wrote: > On Sat, Mar 5, 2016 at 12:59 PM, Greg Stark 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 th

[HACKERS] Re: Static code checker research worth investigating (Communications of the ACM, 03/2016, Vol. 59, No. 03, p. 99)

2016-03-05 Thread Greg Stark
On Sat, Mar 5, 2016 at 12:59 PM, Greg Stark 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 wan

[HACKERS] Re: Static code checker research worth investigating (Communications of the ACM, 03/2016, Vol. 59, No. 03, p. 99)

2016-03-05 Thread Greg Stark
On Sat, Mar 5, 2016 at 12:41 PM, Tomas Vondra 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