Re: Mandates explicit -std=c++XY for c++ projects

2017-10-14 Thread Wouter Verhelst
On Tue, Oct 10, 2017 at 09:26:07AM -0400, Michael Stone wrote: > On Tue, Oct 10, 2017 at 02:16:36PM +0100, Dimitri John Ledkov wrote: > > On 10 October 2017 at 14:07, Gert Wollny wrote: > > > I think nobody would object if you set the flag to -std=c++98 for a > > > certain

Re: Mandates explicit -std=c++XY for c++ projects

2017-10-11 Thread Mathieu Malaterre
On Tue, Oct 10, 2017 at 3:05 PM, Matthias Klose wrote: > On 10.10.2017 12:38, Mathieu Malaterre wrote: >> Mathias, >> >> On Tue, Oct 10, 2017 at 12:25 PM, Matthias Klose wrote: >>> On 10.10.2017 11:42, Mathieu Malaterre wrote: On Tue, Oct 10, 2017 at 11:38

Re: Mandates explicit -std=c++XY for c++ projects

2017-10-10 Thread Michael Stone
On Tue, Oct 10, 2017 at 05:36:47PM +0100, Dimitri John Ledkov wrote: On 10 October 2017 at 14:26, Michael Stone wrote: On Tue, Oct 10, 2017 at 02:16:36PM +0100, Dimitri John Ledkov wrote: On 10 October 2017 at 14:07, Gert Wollny wrote: I think

Re: Mandates explicit -std=c++XY for c++ projects

2017-10-10 Thread Dimitri John Ledkov
On 10 October 2017 at 14:26, Michael Stone wrote: > On Tue, Oct 10, 2017 at 02:16:36PM +0100, Dimitri John Ledkov wrote: >> >> On 10 October 2017 at 14:07, Gert Wollny wrote: >>> >>> I think nobody would object if you set the flag to -std=c++98 for a >>>

Re: Mandates explicit -std=c++XY for c++ projects

2017-10-10 Thread Michael Stone
On Tue, Oct 10, 2017 at 02:16:36PM +0100, Dimitri John Ledkov wrote: On 10 October 2017 at 14:07, Gert Wollny wrote: I think nobody would object if you set the flag to -std=c++98 for a certain package, especially if upstream is dead or unwilling to move to a newer

Re: Mandates explicit -std=c++XY for c++ projects

2017-10-10 Thread Dimitri John Ledkov
On 10 October 2017 at 14:07, Gert Wollny wrote: > Hello Mathieu, > > Am Dienstag, den 10.10.2017, 11:45 +0200 schrieb Mathieu Malaterre: > [...] > I don't think there is much to gain from it. Whenever there is a > change >> > in the major version of gcc/g++ many bugs show up

Re: Mandates explicit -std=c++XY for c++ projects

2017-10-10 Thread Dimitri John Ledkov
On 10 October 2017 at 07:45, Mathieu Malaterre wrote: > Dear all, > > Since the GCC 6 release [1], the default mode for C++ is now > -std=gnu++14 instead of -std=gnu++98. What this means is that upon > (re)compilation a library written for c++98 will be recompiled using a >

Re: Mandates explicit -std=c++XY for c++ projects

2017-10-10 Thread Gert Wollny
Hello Mathieu, Am Dienstag, den 10.10.2017, 11:45 +0200 schrieb Mathieu Malaterre: [...] I don't think there is much to gain from it. Whenever there is a change > > in the major version of gcc/g++ many bugs show up and all involved > > really do a great job fixing these. IMHO switching from an

Re: Mandates explicit -std=c++XY for c++ projects

2017-10-10 Thread Matthias Klose
On 10.10.2017 12:38, Mathieu Malaterre wrote: > Mathias, > > On Tue, Oct 10, 2017 at 12:25 PM, Matthias Klose wrote: >> On 10.10.2017 11:42, Mathieu Malaterre wrote: >>> On Tue, Oct 10, 2017 at 11:38 AM, Matthias Klose wrote: On 10.10.2017 08:45, Mathieu

Re: Mandates explicit -std=c++XY for c++ projects

2017-10-10 Thread Michael Stone
On Tue, Oct 10, 2017 at 12:38:03PM +0200, Mathieu Malaterre wrote: As with Gert's answer, I fail to understand your point: You would prefer to see packages being (re)compiled *without* an explicit -std= flag, so that it always gets recompiled using whatever is the current c++ standard used by

Re: Mandates explicit -std=c++XY for c++ projects

2017-10-10 Thread Mathieu Malaterre
Mathias, On Tue, Oct 10, 2017 at 12:25 PM, Matthias Klose wrote: > On 10.10.2017 11:42, Mathieu Malaterre wrote: >> On Tue, Oct 10, 2017 at 11:38 AM, Matthias Klose wrote: >>> On 10.10.2017 08:45, Mathieu Malaterre wrote: Dear all, Since the GCC

Re: Mandates explicit -std=c++XY for c++ projects

2017-10-10 Thread Matthias Klose
On 10.10.2017 11:42, Mathieu Malaterre wrote: > On Tue, Oct 10, 2017 at 11:38 AM, Matthias Klose wrote: >> On 10.10.2017 08:45, Mathieu Malaterre wrote: >>> Dear all, >>> >>> Since the GCC 6 release [1], the default mode for C++ is now >>> -std=gnu++14 instead of -std=gnu++98.

Re: Mandates explicit -std=c++XY for c++ projects

2017-10-10 Thread Mathieu Malaterre
Hi Gert ! On Tue, Oct 10, 2017 at 11:31 AM, Gert Wollny wrote: > Am Dienstag, den 10.10.2017, 08:45 +0200 schrieb Mathieu Malaterre: > > [...] > With this mind I'd like to make mandatory the -std=c++XY flags when >> compiling either a c++ library or a stand-alone c++

Re: Mandates explicit -std=c++XY for c++ projects

2017-10-10 Thread Matthias Klose
On 10.10.2017 08:45, Mathieu Malaterre wrote: > Dear all, > > Since the GCC 6 release [1], the default mode for C++ is now > -std=gnu++14 instead of -std=gnu++98. What this means is that upon > (re)compilation a library written for c++98 will be recompiled using a > different c++ standard (c++14

Re: Mandates explicit -std=c++XY for c++ projects

2017-10-10 Thread Mathieu Malaterre
On Tue, Oct 10, 2017 at 11:38 AM, Matthias Klose wrote: > On 10.10.2017 08:45, Mathieu Malaterre wrote: >> Dear all, >> >> Since the GCC 6 release [1], the default mode for C++ is now >> -std=gnu++14 instead of -std=gnu++98. What this means is that upon >> (re)compilation a

Re: Mandates explicit -std=c++XY for c++ projects

2017-10-10 Thread Gert Wollny
Am Dienstag, den 10.10.2017, 08:45 +0200 schrieb Mathieu Malaterre: [...] With this mind I'd like to make mandatory the -std=c++XY flags when > compiling either a c++ library or a stand-alone c++ program: > > 1. Either upstream define the explicit -std=c++XY flags by mean of > its build system, >

Re: Mandates explicit -std=c++XY for c++ projects

2017-10-10 Thread Mathieu Malaterre
Ansgar, On Tue, Oct 10, 2017 at 9:17 AM, Mathieu Malaterre wrote: > Ansgar, > > On Tue, Oct 10, 2017 at 9:11 AM, Ansgar Burchardt wrote: >> Mathieu Malaterre writes: >>> With this mind I'd like to make mandatory the -std=c++XY flags when >>> compiling either

Re: Mandates explicit -std=c++XY for c++ projects

2017-10-10 Thread Mathieu Malaterre
[continued] On Tue, Oct 10, 2017 at 9:11 AM, Ansgar Burchardt wrote: > Mathieu Malaterre writes: >> With this mind I'd like to make mandatory the -std=c++XY flags when >> compiling either a c++ library or a stand-alone c++ program: >> >> 1. Either upstream define the explicit

Re: Mandates explicit -std=c++XY for c++ projects

2017-10-10 Thread Andrey Rahmatullin
On Tue, Oct 10, 2017 at 09:12:45AM +0200, Mathieu Malaterre wrote: > > lintian doesn't scan build logs, it scans source and binary packages. > > Right. I always forgot that. What is the mechanism used for > shlib-calls-exit, does it rely on source parsing ? No, it just looks at the imported

Re: Mandates explicit -std=c++XY for c++ projects

2017-10-10 Thread Mathieu Malaterre
Ansgar, On Tue, Oct 10, 2017 at 9:11 AM, Ansgar Burchardt wrote: > Mathieu Malaterre writes: >> With this mind I'd like to make mandatory the -std=c++XY flags when >> compiling either a c++ library or a stand-alone c++ program: >> >> 1. Either upstream define the explicit

Re: Mandates explicit -std=c++XY for c++ projects

2017-10-10 Thread Mathieu Malaterre
On Tue, Oct 10, 2017 at 9:05 AM, Julien Cristau wrote: > On Tue, Oct 10, 2017 at 08:45:49 +0200, Mathieu Malaterre wrote: > >> Dear all, >> >> Since the GCC 6 release [1], the default mode for C++ is now >> -std=gnu++14 instead of -std=gnu++98. What this means is that upon >>

Re: Mandates explicit -std=c++XY for c++ projects

2017-10-10 Thread Ansgar Burchardt
Mathieu Malaterre writes: > With this mind I'd like to make mandatory the -std=c++XY flags when > compiling either a c++ library or a stand-alone c++ program: > > 1. Either upstream define the explicit -std=c++XY flags by mean of its > build system, > 2. Or the package maintainers needs to

Re: Mandates explicit -std=c++XY for c++ projects

2017-10-10 Thread Julien Cristau
On Tue, Oct 10, 2017 at 08:45:49 +0200, Mathieu Malaterre wrote: > Dear all, > > Since the GCC 6 release [1], the default mode for C++ is now > -std=gnu++14 instead of -std=gnu++98. What this means is that upon > (re)compilation a library written for c++98 will be recompiled using a > different