[issue20595] C89 compliance issue in Python/getargs.c

Roundup Robot added the comment: New changeset 417a468ae755 by Benjamin Peterson in branch 'default': remove dynamic initializer lists for c89 compliance (closes #20595) http://hg.python.org/cpython/rev/417a468ae755 -- nosy: +python-dev resolution: -> fixed stage: -> committed/rejected

[issue20595] C89 compliance issue in Python/getargs.c

Benjamin Peterson added the comment: We ought not advertise C89 compliance and not have it. -- ___ Python tracker ___ ___ Python-bugs-

[issue20595] C89 compliance issue in Python/getargs.c

Jeffrey Armstrong added the comment: Depending on your compiler, yes, it is more than a theoretical problem. I am building using the Open Watcom compiler, and it chokes on these initializers due to their non-conformance. I would assume some other obscure, non-GNU/non-MSVC/non-Clang compilers

[issue20595] C89 compliance issue in Python/getargs.c

Larry Hastings added the comment: Is this more than a theoretical problem? -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue20595] C89 compliance issue in Python/getargs.c

Changes by Antoine Pitrou : -- nosy: +benjamin.peterson, larry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue20595] C89 compliance issue in Python/getargs.c

New submission from Jeffrey Armstrong: The file Python/getargs.c currently uses an array initializer with a runtime variable, causing compile errors on strict C89 compilers. The variables named freelist in vgetargs1() and vgetargskeywords() both use non-constant initializers. The attached pa