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 loewis
Recipients jschneid, loewis
Date 2011-07-14.18:29:21
SpamBayes Score 4.71382e-05
Marked as misclassified No
Message-id <1310668162.37.0.350611613951.issue12561@psf.upfronthosting.co.za>
In-reply-to
Content
Why is the __W macro needed?

Please don't call it WCHAR:
- it conflicts with a same-named macro on Windows
- you are applying it to strings, not characters

FWIW, the compiler doesn't conform to standard C if it rejects this code. 6.4.5p4 says

       [#4]   In  translation  phase  6,  the  multibyte  character
       sequences specified by any sequence  of  adjacent  character
       and  wide  string  literal  tokens  are  concatenated into a
       single multibyte character sequence.  If any of  the  tokens
       are  wide  string  literal  tokens,  the resulting multibyte
       character sequence is treated  as  a  wide  string  literal;
       otherwise, it is treated as a character string literal.
History
Date User Action Args
2011-07-14 18:29:22loewissetrecipients: + loewis, jschneid
2011-07-14 18:29:22loewissetmessageid: <1310668162.37.0.350611613951.issue12561@psf.upfronthosting.co.za>
2011-07-14 18:29:21loewislinkissue12561 messages
2011-07-14 18:29:21loewiscreate