Re: Remove pg_strtouint64(), use strtoull() directly

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Remove pg_strtouint64(), use strtoull() directly
Date: 2021-12-14 22:30:11
Message-ID: 557476.1639521011@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> writes:
> OK, makes sense. Here is an alternative patch. It introduces two
> light-weight macros strtoi64() and strtou64() (compare e.g., strtoimax()
> in POSIX) in c.h and removes pg_strtouint64(). This moves the
> portability layer from numutils.c to c.h, so it's closer to the rest of
> the int64 portability code. And that way it is available to not just
> server code. And it resolves the namespace collision with the
> pg_strtointNN() functions in numutils.c.

Works for me. I'm not in a position to verify that this'll work
on Windows, but the buildfarm will tell us that quickly enough.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dag Lem 2021-12-14 22:34:00 Re: daitch_mokotoff module
Previous Message Joshua Brindle 2021-12-14 22:26:24 Re: Granting SET and ALTER SYSTE privileges for GUCs