Re: elog() proposal - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: elog() proposal
Date
Msg-id 200202230057.g1N0vsr19243@candle.pha.pa.us
Whole thread Raw
In response to Re: elog() proposal  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: elog() proposal  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: elog() proposal  (Karel Zak <zakkr@zf.jcu.cz>)
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > OK, so elog(ERROR, ...) and PGError(msg, ...) would be the same.  Makes
> > sense.  Should we consider hiding these in macros so they really still
> > call elog(ERROR, ...) for backward compatiblity?
> 
> I would love to make them macros, but I don't know a portable way to
> create macros with variable numbers of arguments.  Do you feel like
> writing double parens?
> 
>     PGERROR((msg, ...))

Then we have to wonder what PGError is getting us that elog(ERROR)
isn't, except the ability to do internationalization based on the first
parameter.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: elog() proposal
Next
From: Peter Eisentraut
Date:
Subject: Re: elog() proposal