> > Also, the data objects obviously have to be put somewhere. Before > > doing any of this, we need to decide where this stuff belongs. I > > doubt the technical effort involved will be too challenging. > > So we don't need to make a decision today, right? We can delay that > until those easy problems are solved. What about my proposal to get rid of the data objects and add a few isxxx() methods instead? I don't think that the data objects have any other function except for membership testing, and a method can be faster. The method approach will also make locale-awareness easier (since the method can use <ctype.h> which is already locale-aware). --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4