[Python-Dev] Re: [Python-checkins]python/dist/src/Objects unicodeobject.c, 2.197, 2.198 (original) (raw)
Martin v. Löwis martin at v.loewis.de
Thu Sep 18 14:54:25 EDT 2003
- Previous message: [Python-Dev] Re: [Python-checkins]python/dist/src/Objects unicodeobject.c, 2.197, 2.198
- Next message: [Python-Dev] Re: [Python-checkins]python/dist/src/Objects unicodeobject.c, 2.197, 2.198
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
"Tim Peters" <tim.one at comcast.net> writes:
That's fine for gcc then, so long as we don't branch on the contents of uninitialized memory, and we just fixed a bug of that sort.
If PyUNICODE ever resolves to a signed 2-byte type, though, the sign bit is still in play for legit contents.
Right. I agree that we don't want to use a signed 2-byte type. Given that only MS uses a two-byte wchar_t (to my knowledge), and that theirs is unsigned, having an autoconf test to detect that this configuration is not supported is more than enough.
Regards, Martin
- Previous message: [Python-Dev] Re: [Python-checkins]python/dist/src/Objects unicodeobject.c, 2.197, 2.198
- Next message: [Python-Dev] Re: [Python-checkins]python/dist/src/Objects unicodeobject.c, 2.197, 2.198
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]