Compatibility is dead

[Daniel van Vugt]

At the moment, I suspect replacing all destructors:
     virtual ~Foo() = default
with
     virtual ~Foo() {}
and removing various "noexcept" specifiers, would suffice to retain 
gcc-4.7 support.

But I did not propose that change because I know a few people would 
oppose it.

Also, there's a chance that we will start using some other C++11 feature 
in gcc-4.8 that gcc-4.7 lacks. But working around the above destructor 
issue is the primary problem right now.


On 15/07/13 23:57, Mario Rugiero wrote:
> Is there any reference on which C++11 features need to be replaced?
>
>
> 2013/7/15 Daniel van Vugt <daniel.van.vugt at canonical.com
> <mailto:daniel.van.vugt at canonical.com>>
>
>     It finally happened. lp:mir now depends on C++11 features and
>     external packages (google-mock) too heavily to be buildable on
>     raring any more.
>
>     Essentially the main problem is that raring uses gcc-4.7 and Mir's
>     code depends on more complete C++11 features that only work in
>     gcc-4.8. The other issue is that Mir now depends on saucy-specific
>     hacks in the google-mock package, which can't be found elsewhere.
>
>     This is a little disappointing. If anyone would like to take on the
>     project of making the Mir source more backward compatible, then feel
>     free. But maintaining compatibility with raring has now taken up too
>     much of my time...
>
>     - Daniel
>
>     --
>     Mir-devel mailing list
>     Mir-devel at lists.ubuntu.com <mailto:Mir-devel at lists.ubuntu.com>
>     Modify settings or unsubscribe at:
>     https://lists.ubuntu.com/__mailman/listinfo/mir-devel
>     <https://lists.ubuntu.com/mailman/listinfo/mir-devel>
>
>