mal wrote: > =20 > #define Py_UNICODE_MATCH(string, offset, substring)\ > ! ((*((string)->str + (offset)) =3D=3D *((substring)->str)) &&\ > ! !memcmp((string)->str + (offset), (substring)->str,\ > (substring)->length*sizeof(Py_UNICODE))) > =20 I completely forgot that this has different semantics if the substring happens to be empty. (substrings are null terminated, but "\0" isn't the same thing as ""...) don't have time to screen unicodeobject.c right now, but maybe someone else can do it? if not, maybe amk's patch was a better idea after all... </F>
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