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 lemburg
Recipients ezio.melotti, lemburg, stutzbach, theller, vstinner
Date 2010-10-01.13:06:01
SpamBayes Score 5.551115e-17
Marked as misclassified No
Message-id <4CA5DCB5.1080407@egenix.com>
In-reply-to <1285938102.22.0.237782334505.issue8670@psf.upfronthosting.co.za>
Content
Daniel Stutzbach wrote:
> 
> Daniel Stutzbach <daniel@stutzbachenterprises.com> added the comment:
> 
>> You can tweak the Windows pyconfig.h to use UCS4, AFAIK, if you want to
>> test drive this case.
> 
> I seem to recall seeing some other code that assumed Windows implied UCS2.  Proceed with caution. ;-)

Probably, yes. I've never tried it myself.

>> But it's probably easier to configure with "gcc -fshort-wchar" on
>> Linux :-)
> 
> libc will still be using sizeof(wchar_t) == 4, though.  Won't that cause Bad Things to happen when calling libc wide-character functions?

Sure, but this is just about testing an interface, not running
applications :-)

Here's what the GCC man-page has to say:

       -fshort-wchar
           Override the underlying type for wchar_t to be short unsigned int instead
           of the default for the target.  This option is useful for building
           programs to run under WINE.

           Warning: the -fshort-wchar switch causes GCC to generate code that is not
           binary compatible with code generated without that switch.  Use it to
           conform to a non-default application binary interface.
History
Date User Action Args
2010-10-01 13:06:05lemburgsetrecipients: + lemburg, theller, vstinner, stutzbach, ezio.melotti
2010-10-01 13:06:02lemburglinkissue8670 messages
2010-10-01 13:06:01lemburgcreate