➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author skrah
Recipients eric.smith, loewis, pitrou, r.david.murray, skrah, srid
Date 2010-06-19.13:14:58
SpamBayes Score 0.0009866296
Marked as misclassified No
Message-id <20100619131453.GA16155@yoda.bytereef.org>
In-reply-to <4C1CBF87.8080003@v.loewis.de>
Content 
Martin v. Löwis <report@bugs.python.org> wrote:
> > Of course, it is dubious why EOF is not tested separately rather than
> > passing it to Py_ISALNUM(). Micro-optimization? At least a comment
> > should be added.
> 
> No, I think this is an error that EOF is not processed separately.
> Otherwise, char 255 may be confused with EOF.

Indeed. I think Py_ISALNUM() should check for EOF, to be consistent
with the C isalnum(int c).
History
Date User Action Args
2010-06-19 13:15:00skrahsetrecipients: + skrah, loewis, pitrou, eric.smith, r.david.murray, srid
2010-06-19 13:14:58skrahlinkissue9020 messages
2010-06-19 13:14:58skrahcreate