Movatterモバイル変換

[Python-Dev] Windows build - fixing compile warnings before VS2010

• Previous message:[Python-Dev] [Python-checkins] cpython: enable hashrandomization by default
• Next message:[Python-Dev] Windows build - fixing compile warnings before VS2010
• Messages sorted by:[ date ][ thread ][ subject ][ author ]

While some effort has gone on to get the 32-bit build to compilewithout warnings (thanks for that!), 64-bit still has numerouswarnings. Before I push forward on more of the VS2010 port, I'd liketo have a clean 2008 build all around so we can more easily track whatmay have changed. In completing that effort, I'm using a guidelineMartin set out in #9566 [0], and please let me know if there are anyothers to follow. I kind of doubt anyone is against this, but if youare, please speak up before I start pushing changes.While I have your attention, I'd like to throw two other things outthere to follow up the above effort:1. Is anyone opposed to moving up to Level 4 warnings?...take a deep breath...2. Is anyone opposed to enabling warnings as errors?[0]http://bugs.python.org/issue9566#msg113574

• Previous message:[Python-Dev] [Python-checkins] cpython: enable hashrandomization by default
• Next message:[Python-Dev] Windows build - fixing compile warnings before VS2010
• Messages sorted by:[ date ][ thread ][ subject ][ author ]