On Tue, Sep 7, 2010 at 1:31 AM, Robert Bradshaw <[email protected]> wrote:
>> I think it's >> reasonable to either a) require a 'b' prefix in that case or b) enforce >> bytes semantics for char* automatically. To make life easy for users, >> either b) can be applied or for a), we can let Cython generate a patch (or >> script) that prepends 'b' prefixes to all places where unprefixed string >> literals are used in a char* context. That way, the source code becomes >> safe regardless of the unicode_literals setting. > > Neither are obvious to do for a newcomer, whereas a compiler error can > give a hint. Nevermind, if we require a 'b' prefix, the fix would be obvious to a newcomer, though not the best first impression. It's the shifting string literal interpretation that worries me most. - Robert _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
