Antoine Pitrou <pit...@free.fr> added the comment: > 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 :) ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue9036> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
