Re: pgsql: Clarify coding of .exe patch

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Neil Conway <neilc(at)samurai(dot)com>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Clarify coding of .exe patch
Date: 2004-11-01 06:29:24
Message-ID: 5424.1099290564@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Neil Conway <neilc(at)samurai(dot)com> writes:
> While I still think we're on pretty solid ground assuming this
> optimization is going to be made, I'm fine with defining something like
> const_strlen() that uses sizeof(). Also, we can guard against programmer
> mistakes via __builtin_constant_p() when using GCC.

I think both you and Bruce are missing the really fundamental point
here. You are both optimizing on the grounds that there is no god but
RMS and his prophet is GCC. I have a somewhat wider view of which
compilers we want to target.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Neil Conway 2004-11-01 06:45:18 Re: pgsql: Clarify coding of .exe patch
Previous Message Neil Conway 2004-11-01 06:17:10 Re: pgsql: Clarify coding of .exe patch