Re: Automatic code conversion between UNICODE and other encodings - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Automatic code conversion between UNICODE and other encodings
Date
Msg-id 26144.971362215@sss.pgh.pa.us
Whole thread Raw
In response to Automatic code conversion between UNICODE and other encodings  (Tatsuo Ishii <t-ishii@sra.co.jp>)
List pgsql-hackers
Tatsuo Ishii <t-ishii@sra.co.jp> writes:
> P.S. I have used bsearch() to search code spaces. Is bsearch() is
> portable enough?

According to my references, bsearch() was originally a SysV localism
but is a required library function in ANSI C.  So in theory it should
be portable enough ... but I notice we have implementations in
backend/ports for strtol() and strtoul() which are also required by
ANSI C, so apparently some people are or were running Postgres on
machines that are a few bricks shy of a full ANSI library.

I suggest waiting to see if anyone complains.  If so, we should be
able to write up a substitute bsearch() and add it to ports/.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Re: [GENERAL] postgresql 7.1
Next
From: Peter Eisentraut
Date:
Subject: Re: Re: [GENERAL] +/- Inf for float8's