apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe, Jr." <wr...@rowe-clan.net>
Subject Re: freezing 1.3 tonight
Date Thu, 01 May 2008 23:52:58 GMT
Lucian Adrian Grijincu wrote:
> On Fri, May 2, 2008 at 2:18 AM, Roy T. Fielding <fielding@gbiv.com> wrote:
>>  Why?  The type char is defined by the C standard to be an 8bit signed integer.
>>  The type unsigned char is defined to be an 8bit unsigned integer.  Why would
>>  we want to add a bunch of unnecessary casting?
> 
> Not quite: http://home.att.net/~jackklein/c/inttypes.html

That doesn't resolve Roy's question of "why overload signed char and
unsigned char"?

Can anyone point to a platform where int8_t/uint8_t != signed/unsigned char?
If so, I agree with the patch.

If not... Roy's question remains.

Bill

Mime
View raw message