[issue10310] signed:1 bitfields rarely make sense

2014-06-18 Thread Berker Peksag
Changes by Berker Peksag berker.pek...@gmail.com: -- resolution: - fixed stage: patch review - resolved status: open - closed versions: +Python 3.5 -Python 2.7, Python 3.1, Python 3.2 ___ Python tracker rep...@bugs.python.org

[issue10310] signed:1 bitfields rarely make sense

2014-06-17 Thread Mark Lawrence
Mark Lawrence added the comment: Could we have a patch review on this please. -- nosy: +BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10310 ___

[issue10310] signed:1 bitfields rarely make sense

2014-06-17 Thread Roundup Robot
Roundup Robot added the comment: New changeset 3aeca1fd4c0e by Victor Stinner in branch 'default': Issue #10310: Use unsigned int field:1 instead of signed int field:1 in a http://hg.python.org/cpython/rev/3aeca1fd4c0e -- nosy: +python-dev ___ Python

[issue10310] signed:1 bitfields rarely make sense

2010-11-04 Thread Hallvard B Furuseth
New submission from Hallvard B Furuseth h.b.furus...@usit.uio.no: In Python 2.7 and 3.2a3, Modules/_io/textio.c uses signed:1 bitfields. They have value -1 or 0 in two's complement, but are not used thus here: gcc complains of bitfield = 1 overflow. If the point was that they are assigned

[issue10310] signed:1 bitfields rarely make sense

2010-11-04 Thread STINNER Victor
Changes by STINNER Victor victor.stin...@haypocalc.com: -- nosy: +haypo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10310 ___ ___

[issue10310] signed:1 bitfields rarely make sense

2010-11-04 Thread Antoine Pitrou
Changes by Antoine Pitrou pit...@free.fr: -- nosy: +amaury.forgeotdarc stage: - patch review versions: +Python 2.7, Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10310 ___