Re: pgsql: Add pg_strnlen() a portable implementation of strlen.

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Add pg_strnlen() a portable implementation of strlen.
Date: 2017-10-10 20:53:15
Message-ID: 20171010205315.g7l6tf3j5jzplqax@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On 2017-10-10 16:51:39 -0400, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > As far as I can tell it's still somehow using a configure from before
> > the last commits:
>
> No, it's pilot error. The AC_CHECK_FUNCS call you added strnlen to
> is only executed if
> AS_IF([test "$enable_thread_safety" = yes -a "$PORTNAME" != "win32"],

Dear god, I'm daft. Dear god, m4 is a horrible lanuagage.

Thanks.

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Andrew Dunstan 2017-10-10 21:34:17 Re: pgsql: Add pg_strnlen() a portable implementation of strlen.
Previous Message Tom Lane 2017-10-10 20:51:39 Re: pgsql: Add pg_strnlen() a portable implementation of strlen.