Re: Automatic code conversion between UNICODE and other encodings

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Automatic code conversion between UNICODE and other encodings
Date: 2000-10-12 14:50:15
Message-ID: 26144.971362215@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2000-10-12 14:51:57 Re: [HACKERS] Re: postgresql 7.1
Previous Message Peter Eisentraut 2000-10-12 14:46:08 Re: 7.0.2 on Solaris