Awesome! Looks like that solves the problem. (Also, 'aww shucks!', I was hoping we'd choose #1 and I'd get to use some more C++11 :) )
On Fri, 2015-07-24 at 01:48 +0900, ???(Uze Choi) wrote: > I'll let the service Code fixed to be compatible to 4.6 by today. > > BR, Uze Choi > -----Original Message----- > From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev- > bounces at lists.iotivity.org] On Behalf Of Keane, Erich > Sent: Friday, July 24, 2015 1:42 AM > To: Macieira, Thiago > Cc: iotivity-dev at lists.iotivity.org > Subject: Re: [dev] GCC/G++ Version > > I think the solution is one of 2: > > 1- Just decide as a project to change compilers to 4.8, giving us full and > true C++11 support > 2- "Fix" the service unit tests to no longer require the C++11 features not > available in 4.6 > > Anything else is just going to cause issues. The override keyword (as > Thiago implied with his define) is a great feature, but nothing that > couldn't be removed from the code without issue. > > > On Thu, 2015-07-23 at 09:37 -0700, Thiago Macieira wrote: > > On Thursday 23 July 2015 09:31:09 Lankswert, Patrick wrote: > > > Thiago, > > > > > > Will a developer that wants to build the stack need to have two > compilers? > > > > I don't think so. > > > > > If we use only one compiler, how do we ensure that 4.8 features do > > > not creep into the stack that prohibits compilation under 4.6? > > > > I'd say we add a build to Jenkins that uses 4.6, with tests disabled. > > If you break the build, you don't get Jenkins's +1. > > > > _______________________________________________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev >
