| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Win64 warnings about size_t |
| Date: | 2010-01-01 17:47:49 |
| Message-ID: | 2406.1262368069@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> My first 5-6 checks of where these happen are all cases where we
> assign the result of strlen() something to an int, or call a function
> taking an int as parameter with the result of strlen() in there.
Yeah. Getting rid of all those cases is impractical I think, and
pointless anyway --- we have limitations in palloc and Datum
representation that ensure we'll never be dealing with strings (or other
values) larger than 1GB.
> strlen() returns size_t, which AFAICS is per the standard and not even
> a Microsoft-specific idea.
Correct.
> So I don't really see what win64 does differently in this case, but
> perhaps I've been looking at this code too long? Or is it simply that
> MSVC warns about this and GCC doesn't, and I shuld disbale the
> warning?
I think MSVC is just complaining about something gcc doesn't. If you
can disable this specific warning it'd be a good plan.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2010-01-01 17:50:31 | Re: Win64 warnings about size_t |
| Previous Message | Simon Riggs | 2010-01-01 17:42:44 | Re: Cancelling idle in transaction state |