Message 412690 - 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.

Author	vstinner
Recipients	vstinner
Date	2022-02-06.23:52:36
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1644191556.12.0.192524677903.issue46670@roundup.psfhosted.org>
In-reply-to

Content
Building Python with "gcc -Wundef" emits many warnings about usage of undefined macros. If a macro is not defined, it is equal to 0. The problem is that a macro can be undefined because of a missing #include, or because of a typo in its name, or because "#ifdef MACRO" should be used instead of "#if MACRO". It can hide bugs. I plan to fix these warnings.

Building Python with "gcc -Wundef" emits many warnings about usage of undefined macros. If a macro is not defined, it is equal to 0.

The problem is that a macro can be undefined because of a missing #include, or because of a typo in its name, or because "#ifdef MACRO" should be used instead of "#if MACRO". It can hide bugs.

I plan to fix these warnings.

History
Date	User	Action	Args
2022-02-06 23:52:36	vstinner	set	recipients: + vstinner
2022-02-06 23:52:36	vstinner	set	messageid: <1644191556.12.0.192524677903.issue46670@roundup.psfhosted.org>
2022-02-06 23:52:36	vstinner	link	issue46670 messages
2022-02-06 23:52:36	vstinner	create