>>
>> * inline function
>> static inline function can be used instead of may macros.
>> It is more readable, and type safe.
>
> My experience from a few months ago with some cross-platform code is
> that clang, GCC and MSVC have different ideas about how inline
> functions in C work. Are they stati
> Message: 2
> Date: Sat, 6 Aug 2016 14:27:15 +0900
> From: INADA Naoki
> To: Guido van Rossum
> Cc: Ned Deily , Python-Dev
> Subject: Re: [Python-Dev] C99
> Message-ID:
>
> Content-Type: text/plain; charset=UTF-8
>
> I think these features may improve C code readability.
> (Easy featur
Guido van Rossum wrote:
> This feels close to a code of conduct violation. This kind of language
> may be okay on the Linux kernel list, but I don't see the point of it
> here.
Sorry, I should have found a more diplomatic formulation. But the principle
remains, build problems araising from missi
On Sat, Aug 6, 2016 at 5:55 PM, Sturla Molden wrote:
> Either they install Xcode or they
> don't get to build anything.
I always thought "Command Line Tools" would be enough.
https://developer.apple.com/library/ios/technotes/tn2339/_index.html#//apple_ref/doc/uid/DTS40014588-CH1-WHAT_IS_THE_COMM
On Sat, Aug 6, 2016 at 2:55 PM, Sturla Molden wrote:
> Xcode must be installed to build anything on Mac. It is not optional. Users
> who need to build Python without installing Xcode need to fix their heads.
> Because that is where their problem resides. There is no remedy for
> stubbornness to th
On Aug 6, 2016, at 17:55, Sturla Molden wrote:
> On OSX 10.8 and earlier, the default CC is llvm-gcc-4.2.1, available as the
> gcc command. clang is also installed, so we can always
[...]
Thanks, but this is getting way off-topic. I am well aware of what compilers
are available on what release
"Stephen J. Turnbull" wrote:
> I may be talking through my hat here, but Apple has been using LLVM
> for several major releases now. They seem to be keeping the GCC
> frontend stuck at 4.2.1, though. So just because we've been using GCC
> 4.2.1 on Mac, including on buildbots, doesn't mean that
Ned Deily wrote:
> On Aug 6, 2016, at 01:16, Stephen J. Turnbull
> wrote:
>> I may be talking through my hat here, but Apple has been using LLVM
>> for several major releases now. They seem to be keeping the GCC
>> frontend stuck at 4.2.1, though. So just because we've been using GCC
>> 4.2.1
On Sat, 6 Aug 2016 at 10:16 Ned Deily wrote:
> On Aug 6, 2016, at 00:04, Guido van Rossum wrote:
> > Different question. What features are we actually talking about? Is it
> > possible to enumerate them?
> >
> > The only thing I'm aware of is declarations following non-declarations
> > in the sa
On Aug 6, 2016, at 00:04, Guido van Rossum wrote:
> Different question. What features are we actually talking about? Is it
> possible to enumerate them?
>
> The only thing I'm aware of is declarations following non-declarations
> in the same block, but I'm no C expert any more.
I'm certainly not
On Aug 6, 2016, at 01:16, Stephen J. Turnbull
wrote:
> I may be talking through my hat here, but Apple has been using LLVM
> for several major releases now. They seem to be keeping the GCC
> frontend stuck at 4.2.1, though. So just because we've been using GCC
> 4.2.1 on Mac, including on build
Ned Deily writes:
> I don't think OS X support should be a gating factor in deciding to
> move ahead with C99 adoption but it does point out that there might
> be more ramifications to this decision.
I may be talking through my hat here, but Apple has been using LLVM
for several major releases
Matthias Klose wrote:
> GCC 5 and GCC 6 default to C11 (-std=gnu11), does the restriction to C99 mean
> that -std=gnu99 should be passed explicitly?
Also note that -std=c99 is not the same as -std=gnu99. The latter allows
GNU extensions like computed goto. Does the interpreter depend on those?
(
On 06.08.2016 00:27, Brett Cannon wrote:
> On Fri, 5 Aug 2016 at 15:17 Guido van Rossum wrote:
>
>> I want it to list specific versions that are known to be good right
>> now, so we can point fingers appropriately when a regression happens.
>>
>
> OK, then we could pin it to MSVC 2016, gcc 6.1,
14 matches
Mail list logo
