[Python-Dev] Can we use "designated initializer" widely incoremodules?

[Steve Dower]

As well as pre-C99 compilers, there are also C++ compilers to think of.

It may be easier to identify the likely features we want to avoid and regex find them in the test suite. Combined with code reviews and the fact that we can change syntax in the header files whenever we want without impact (and if that's not true, let's definitely add checks for those cases), I think we can achieve this without excessive effort.

(And I'm fairly sure MSVC 9.0 in C mode is the most regressive compiler we have available ;) )

Cheers,
Steve

Top-posted from my Windows Phone

-----Original Message-----
From: "Larry Hastings" <larry at hastings.org>
Sent: ‎1/‎17/‎2017 17:02
To: "Python-Dev" <python-dev at python.org>
Subject: Re: [Python-Dev] Can we use "designated initializer" widely incoremodules?


On 01/17/2017 04:48 PM, INADA Naoki wrote:

On Wed, Jan 18, 2017 at 8:48 AM, Larry Hastings <larry at hastings.org> wrote:
While that's a reasonable policy, unless we have a way to automatically
detect that I suspect C99 stuff will creep into the header files and break
the non-C99 customers.  Maybe we could get some sort of buildbot that
exercises this scenario?

How about `gcc -ansi` ?
That seems like it should work fine.  Perhaps we could even add this gcc -ansi step to the normal Python build process.  It shouldn't take very long, so it wouldn't slow down the build very much, and since most Python development happens on UNIX platforms (I think) this would help prevent more C99 constructs from creeping into the header files.


/arry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20170117/2688e308/attachment-0001.html>