Giles Lean <[EMAIL PROTECTED]> writes:
> Portable code uses 'unsigned char' when using ctype.h features, even
> though for many platforms where 'char' is an unsigned type it's not
> necessary for correct functioning.
Yup. Awhile back I went through the PG sources and made sure we
explicitly caste
On 12 Oct 2002 at 8:54, Giles Lean wrote:
> Portable code uses 'unsigned char' when using ctype.h features, even
> though for many platforms where 'char' is an unsigned type it's not
> necessary for correct functioning.
>
> I don't see any isspace() or similar in the code though, so I'm not
> sur
> Well, this is not related to postgresql exactly but to summerise the
> problem, with libc patch PHCO_19090 or compatible upwards, on
> HP-UX11, isspace does not work correctly if input value is >127.
o isspace() and such are defined in the standards to operate on characters
o for historic C rea
On 10 Oct 2002 at 15:30, Manfred Koizar wrote:
> On Wed, 09 Oct 2002 10:00:03 +0200, I wrote:
> >here is an implementation of a set of user types: char3, char4,
> >char10.
>
> New version available. As I don't want to spam the list with various
> versions until I get it right eventually, you ca
On Wed, 09 Oct 2002 10:00:03 +0200, I wrote:
>here is an implementation of a set of user types: char3, char4,
>char10.
New version available. As I don't want to spam the list with various
versions until I get it right eventually, you can get it from
http://members.aon.at/pivot/pg/fixchar20021010
