Message 183877 - Python tracker

➜

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.

In-reply-to
Author	Jeffrey.Armstrong
Recipients	Jeffrey.Armstrong
Date	2013年03月10日.14:18:23
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1362925103.81.0.892590106021.issue17391@psf.upfronthosting.co.za>

Content
When compiling Modules/_cursesmodule.c as a static module with GCC 2.95.3, an error is encountered on line 2260 in PyCurses_GetWin. The error occurs because the PyCursesInitialised macro appears prior _Py_IDENTIFIER(read), which is actually a variable declaration. Switching the order of the statements fixes the issue. In all other functions within Modules/_cursesmodule.c, PyCursesInitialised always appears after all variable declarations. This bug was encountered on the platform m68k-atari-mint using Python 3.3.0 and GCC 2.95.3.

Content

When compiling Modules/_cursesmodule.c as a static module with GCC 2.95.3, an error is encountered on line 2260 in PyCurses_GetWin. The error occurs because the PyCursesInitialised macro appears prior _Py_IDENTIFIER(read), which is actually a variable declaration. Switching the order of the statements fixes the issue.
In all other functions within Modules/_cursesmodule.c, PyCursesInitialised always appears after all variable declarations.
This bug was encountered on the platform m68k-atari-mint using Python 3.3.0 and GCC 2.95.3.

History
Date	User	Action	Args
2013年03月10日 14:18:23	Jeffrey.Armstrong	set	recipients: + Jeffrey.Armstrong
2013年03月10日 14:18:23	Jeffrey.Armstrong	set	messageid: <1362925103.81.0.892590106021.issue17391@psf.upfronthosting.co.za>
2013年03月10日 14:18:23	Jeffrey.Armstrong	link	issue17391 messages
2013年03月10日 14:18:23	Jeffrey.Armstrong	create

homepage