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

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

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: Sat, 24 Sep 2005 13:13:00 -0400
  • Message-id: <13586(dot)1127581980(at)sss(dot)pgh(dot)pa(dot)us>

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



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group