Martin v. Löwis wrote: > Neal Norwitz wrote: >> I'll leave this decision to Martin or someone else, since I'm not >> familiar with the ramifications. Since it was documented as unsigned, >> I think it's reasonable to consider changing. Though it could create >> signed-ness warnings in other modules. I'm not sure but it's possible >> it could create problems for C++ compilers since they are pickier. > > My concern is not so much that it becomes unsigned in 2.4.4, but that > it stops being a typedef for wchar_t on Linux. C++ code that uses that > assumption might stop compiling.
I'd argue that such code is broken anyway: 3rd party code simply cannot make any assumptions on the typedef behind Py_UNICODE. Note that you'd only see this change when compiling Python in the non-standard UCS4 setting on Linux. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Apr 14 2006) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
