Re: ssize_t vs win64

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: 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:36:20
Message-ID: 20716.1262475380@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Sun, Jan 3, 2010 at 00:20, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
>> Seems kind of buggy. They shouldn't be defining it at all.

> Why not? Should they just stop using it? In that case, so should we, no?

What's buggy is M$ failing to provide it in their <sys/types.h> header.
It's unlikely they'll pay any attention to our opinions, however.

I think the Python guys are up against the same problem as us, namely
substituting for the platform's failure to define the type.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2010-01-02 23:40:07 Re: ssize_t vs win64
Previous Message Magnus Hagander 2010-01-02 23:24:51 Re: ssize_t vs win64