Heikki Linnakangas <hlinnakan...@vmware.com> writes: > On 02/01/2015 03:56 PM, Martijn van Oosterhout wrote: >> If you want the compiler to catch this, I don't see any way without >> requiring the code to indicate specifically which local variables it >> intends to use, or not using the locals at all by using a seperate >> cleanup function (as discussed elsewhere in this thread). With >> information about the locals you might be able to conjure some GCC >> macros to set things up to complain if you use anything else.
> I wonder how difficult it would be to teach e.g. clang static analyzer > to catch this, rather than the compiler. Maybe we could interest the Coverity crew in this topic. Seems like the kind of thing they should care about. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers