Skip site navigation (1) Skip section navigation (2)

Re: Proposed patch to clean up signed-ness warnings

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>
Cc: t-ishii(at)sra(dot)co(dot)jp, pgsql-patches(at)postgresql(dot)org,pgsql-hackers(at)postgresql(dot)org
Subject: Re: Proposed patch to clean up signed-ness warnings
Date: 2005-09-24 17:13:00
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-patches
Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> writes:
>> Are you proposing that we change all the "char *" to "unsigned char *"?

> No, I suggest we change all "char *" to "unsigned char *" only where
> it points a string which could hold non ASCII character strings.

Which is pretty nearly all of them...

> To support multiple charsets/collataions, I think we need to change
> the way to represent character strings from the unstructured "char *"
> to more intelligent structure (I know it's hard to implement that
> without significant performance loss, but I know we should do it in
> the future).

Yeah, it's still not clear where we are going to end up, but in the
meantime we've got a lot of warnings cluttering the code and making
it hard to spot real problems.

> So "unsigned char*" is not enough for the goal anyway, I'm not against
> your patches.

OK.  No one else objected, so I'll go ahead and apply before the code
drifts to the point of breaking the patch.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Andrew DunstanDate: 2005-09-24 19:14:03
Subject: Re: 2 forks for md5?
Previous:From: Alvaro HerreraDate: 2005-09-24 16:38:52
Subject: Re: 64-bit API for large objects

pgsql-patches by date

Next:From: Martijn van OosterhoutDate: 2005-09-24 21:45:08
Subject: \x output blowing up
Previous:From: Satoshi NagayasuDate: 2005-09-24 06:07:12
Subject: monitoring sort activities

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group