Message108235
> Thus,
> ((unsigned char)((c) & 0xff)) and ((unsigned char)(c)) should produce
> the same results.
If it's the case, it's probably optimized away by the compiler anyway.
> There is no reason not to do the cast when __CHAR_UNSIGNED__ is
> defined (it will be a no-op).
Agreed. It also reduces the opportunity for bugs :) |
|
Date |
User |
Action |
Args |
2010-06-20 13:27:04 | pitrou | set | recipients:
+ pitrou, loewis, eric.smith, skrah |
2010-06-20 13:27:04 | pitrou | set | messageid: <1277040424.45.0.292669416337.issue9036@psf.upfronthosting.co.za> |
2010-06-20 13:27:02 | pitrou | link | issue9036 messages |
2010-06-20 13:27:02 | pitrou | create | |
|