X-Original-To: pgsql-hackers@postgresql.org Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id CE22947580B; Thu, 13 Mar 2003 16:20:23 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.8/8.12.8) with ESMTP id h2DLKLub009377; Thu, 13 Mar 2003 16:20:21 -0500 (EST) To: Larry Rosenman Cc: pgsql-hackers@postgresql.org, pgsql-interfaces@postgresql.org Subject: Re: Upgrading the backend's error-message infrastructure In-reply-to: <73290000.1047590020@lerlaptop.lerctr.org> References: <9168.1047588660@sss.pgh.pa.us> <73290000.1047590020@lerlaptop.lerctr.org> Comments: In-reply-to Larry Rosenman message dated "Thu, 13 Mar 2003 15:13:40 -0600" Date: Thu, 13 Mar 2003 16:20:21 -0500 Message-ID: <9376.1047590421@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200303/570 X-Sequence-Number: 36816 Larry Rosenman writes: > __FUNCTION__ or an equivalent is MANDATED by C99, and available on > UnixWare's native cc. > You might want to make a configure test for it. Right, __func__ is the C99 spelling. I did have a configure test in mind here: __func__ or __FUNCTION__ or NULL is what would get compiled in. One nice thing about this approach is that we need change only one place to adjust the set of behind-the-scenes error parameters. regards, tom lane