[Python-Dev] C99
Guido van Rossum
guido at python.org
Sun Jun 5 22:52:52 EDT 2016
More information about the Python-Dev mailing list
Sun Jun 5 22:52:52 EDT 2016
- Previous message (by thread): [Python-Dev] C99
- Next message (by thread): [Python-Dev] C99
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I'm not sure I meant that. But if I have a 3rd party extension that compiles with 3.5 headers using C89, then it should still compile with 3.6 headers using C99. Also if I compile it for 3.5 and it only uses the ABI it should still be linkable with 3.6. On Sun, Jun 5, 2016 at 7:42 PM, Sturla Molden <sturla.molden at gmail.com> wrote: > <tritium-list at sdamon.com> wrote: > >> I share Guido's priority there - source compatibility is more important than >> smoothing a few of C's rough edges. Maybe the next breaking change release >> this should be considered (python 4000... python 5000?) > > I was simply pointing out that Guido's priority removes a lot of the > usefulness of C99 at source level. I was not saying I disagreed. If we have > to keep header files clean of C99 I think this proposal just adds clutter. > > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: https://mail.python.org/mailman/options/python-dev/guido%40python.org -- --Guido van Rossum (python.org/~guido)
- Previous message (by thread): [Python-Dev] C99
- Next message (by thread): [Python-Dev] C99
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list