Re: ssize_t vs win64

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(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-03 00:01:14
Message-ID: 201001030001.o0301E519189@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> 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.

Well, I saw two definitions listed in this thread, and it wasn't clear
to me the Python one was known to be the correct one:

PostgreSQL has it as
typedef long ssize_t;

And python has it as:
typedef __int64 ssize_t;

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-01-03 00:02:30 Re: ssize_t vs win64
Previous Message Tom Lane 2010-01-02 23:45:19 Re: ssize_t vs win64