[Bug 269] Many compiler warnings with gcc 4.0

[Steven Simon]

I tend to think this is the wrong approach. By convention, C strings  
are signed and Pascal strings (I know, nobody uses them anymore) are  
unsigned. If char defaults to unsigned, it could cause more problems  
than it solves. We want the compiler to tell us if we're mixing C- 
strings and data buffers. I agree with the other list members who  
don't like the casts. My question is, why is the strvalue field  
unsigned? Does it ever contain data that's not a C-string?

Steve


On Aug 30, 2005, at 12:56 PM, Alan DeKok wrote:

>> What might solve this better is if we can somehow get char to  
>> default to
>> unsigned when building, and all these will go away.
>
>   Sure.