New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
./configure --with-stdc89 to test ANSI C conformity #48808
Comments
The patch adds a configure option --with-stdc89. It also fixes some edge I'm planning to add the configure option to the build bots in order to |
Patch looks good. |
The updated patch moves the compiler option to the right place. |
There is no reason to overload configure script. Please look into pyport.h :
#define Py_LOCAL(type) static type
#define Py_LOCAL_INLINE(type) static inline type Someone add USE_INLINE - not finished. |
I think you don't get the point of the patch. The configure option The patch is meant for testing the Python code on the build bots. |
Christian did you like to propose a separate configure flag for every |
P.S. About C++ comments ( // ) I think that another issue is already |
Python core code must be compliant with the C89 standard but we don't You can verify my patch by adding a // comment somewhere in the code and |
make EXTRA_CFLAGS='-std=c89' works for me. |
:-( the last my comment is incomplete : work for me after "minimal patch" |
Socket module need to be patched too otherwise test_socket fail on UNIX After clean build and with new patch the regression tests results are: Interesting for failed tests is that every succeed if run independently. |
Issue with inline was resolved by configure macro. |
Is it still useful to ensure that ISO C89 compilers are supported in 2011? |
Yes, vs2008 requires that variables must be declared at the start of a block, and IIRC there is a AIX compiler that does not allow // comments. |
Updated patch for Python 3.4. The feature is still useful. For example I found a bug in pymacro.h and fixed it in r84306. |
Make that r6915dfddb3f6 |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: