Author erikjanss
Recipients Alex.Willmer, erikjanss, eryksun, methane, miss-islington, paul.moore, steve.dower, tim.golden, zach.ware
Date 2018-08-16.22:20:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1534458011.67.0.56676864532.issue34217@psf.upfronthosting.co.za>
In-reply-to
Content
As I understand it, if mingw-w64 would change to camelcase headers, it would break backwards compatibility, since a lot of windows source code uses file names in includes that differ from those on this, which works in MSVC, so it goes unnoticed.  There is no good solution.

Even if camelcase headers would be available, the CPython source code would break in much more places.

I agree that it would be strange to have a style rule for a specific toolset, however mixing different styles is even stranger.

The current situation is that 100% of the windows includes are lowercase and allow cross compilation.  I would tend to see that as an advantage.

If a more comprehensive solution would be available, that would be ideal of course.
History
Date User Action Args
2018-08-16 22:20:11erikjansssetrecipients: + erikjanss, paul.moore, tim.golden, methane, zach.ware, eryksun, steve.dower, Alex.Willmer, miss-islington
2018-08-16 22:20:11erikjansssetmessageid: <1534458011.67.0.56676864532.issue34217@psf.upfronthosting.co.za>
2018-08-16 22:20:11erikjansslinkissue34217 messages
2018-08-16 22:20:11erikjansscreate