Re: ssize_t vs win64

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ssize_t vs win64
Date: 2010-01-02 23:45:19
Message-ID: 21244.1262475919@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Tom Lane wrote:
>> I think the Python guys are up against the same problem as us, namely
>> substituting for the platform's failure to define the type.

> I am unclear if accepting what Python chose as a default is the right
> route vs. doing more research.

What exactly do you think we might do differently? There is only one
sane definition for ssize_t on a 64-bit platform.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2010-01-03 00:01:14 Re: ssize_t vs win64
Previous Message Bruce Momjian 2010-01-02 23:40:07 Re: ssize_t vs win64