Re: Assert for frontend programs?

Andrew Dunstan <andrew@dunslane.net>

From: Andrew Dunstan <andrew@dunslane.net>

To: Peter Eisentraut <peter_e@gmx.net>

Cc: Tom Lane <tgl@sss.pgh.pa.us>, Heikki Linnakangas <hlinnakangas@vmware.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>

Date: 2012-12-16T14:56:01Z

Lists: pgsql-hackers

On 12/16/2012 01:29 AM, Peter Eisentraut wrote:
> On Fri, 2012-12-14 at 17:03 -0500, Tom Lane wrote:
>> Having the layer is a good thing, eg so that USE_ASSERT_CHECKING
>> can control it, or so that somebody can inject a different behavior
>> if they want.
> You could also (or at least additionally) map !USE_ASSERT_CHECKING to
> NDEBUG.  This would also help with imported code that calls assert()
> directly.


We should probably do that for both frontend and backend code, no? That 
would get rid of potential problems we already have like inet_net_pton.c 
that I noted the other day.

cheers

andrew