On Fri, 2004-09-24 at 11:53, Tom Lane wrote:
> Ideally I'd like it warning-free on everything, but I'm not sure how
> practical that is. The main thing that non-gcc compilers tend to warn
> about in my experience is "char *" vs "unsigned char *", of which there
> are a lot of occurrences in and around the multibyte code. This does
> not really seem worth cleaning up at the moment.
Per the recent GCC 4.0 report on -hackers, it seems GCC4 will now warn
about char * vs. unsigned char *, so perhaps it is time to clean that
up...
-Neil