Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> It seems risky to me to define macros that are in the
> >> reserved-for-system-use namespace. Who knows what might break in the
> >> system headers if we did that?
>
> > I see we already do this in solaris.h:
>
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> It seems risky to me to define macros that are in the
>> reserved-for-system-use namespace. Who knows what might break in the
>> system headers if we did that?
> I see we already do this in solaris.h:
Mph. Well, at least that's rest
Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > On Mon, Dec 22, 2003 at 06:36:32PM -0500, Bruce Momjian wrote:
> >> Seems we have to test for __alpha and __alpha_. This applied patch
> >> makes that consistent.
>
> > Won't something like the following work?
>
> > #ifdef(__alpha)
Bruce Momjian <[EMAIL PROTECTED]> writes:
> OK, removed __alpha__ tests from main.c, and documented that they aren't
> being used, so we know it is a concious decision. I left the __alpha__
> in s_lock.h because of course that is generic.
Fair enough --- I was mostly worried about the NOFIXADE co
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> example, we have *no* evidence to suggest that that NOFIXADE stuff in
> >> main.c is needed on platforms that don't define __alpha. I would tend
> >> to take an "if it ain't broke don't fix it" approach, especiall
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> example, we have *no* evidence to suggest that that NOFIXADE stuff in
>> main.c is needed on platforms that don't define __alpha. I would tend
>> to take an "if it ain't broke don't fix it" approach, especially on
>> platforms we don't
Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > On Mon, Dec 22, 2003 at 06:36:32PM -0500, Bruce Momjian wrote:
> >> Seems we have to test for __alpha and __alpha_. This applied patch
> >> makes that consistent.
>
> > Won't something like the following work?
>
> > #ifdef(__alpha)
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> On Mon, Dec 22, 2003 at 06:36:32PM -0500, Bruce Momjian wrote:
>> Seems we have to test for __alpha and __alpha_. This applied patch
>> makes that consistent.
> Won't something like the following work?
> #ifdef(__alpha)
> #define __alpha__ 1
> #endif
Alvaro Herrera wrote:
> On Mon, Dec 22, 2003 at 06:36:32PM -0500, Bruce Momjian wrote:
> > Seems we have to test for __alpha and __alpha_. This applied patch
> > makes that consistent.
>
> Won't something like the following work?
>
> #ifdef(__alpha)
> #define __alpha__ 1
> #endif
>
> so you onl
On Mon, Dec 22, 2003 at 06:36:32PM -0500, Bruce Momjian wrote:
> Seems we have to test for __alpha and __alpha_. This applied patch
> makes that consistent.
Won't something like the following work?
#ifdef(__alpha)
#define __alpha__ 1
#endif
so you only have to test for one of them? Just an ide
Seems we have to test for __alpha and __alpha_. This applied patch
makes that consistent.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your bac
11 matches
Mail list logo