On 14 April 2018 at 15:38, Murray Cumming wrote:
> On Thu, 2018-04-12 at 21:10 +0100, Jonathan Wakely wrote:
>> On 12 April 2018 at 21:02, Murray Cumming wrote:
>> > I've just released a version of libsigc++-3.0 (currently unstable)
>> > that
>> > requires C++17. This means that gtkmm-4.0 (currently unstable)
>> > requires
>> > C++17 too. I should have mentioned it first, but I think this is
>> > fine.
>>
>> What are you using from C++17?
>
> Nothing major. Just some constexpr if, std::apply() and std::invoke():
> https://github.com/libsigcplusplus/libsigcplusplus/commits/master
That's fine then - no ABI worries with those bits.
>> GCC's C++17 implementation is not stable yet, so there are still ABI
>> changes possible between GCC 8 and GCC 9.
>>
>> IIRC we've already introduced some (minor) incompatibilities between
>> the std::variant in GCC 7 and GCC 8.
>
> gtkmm-4.0 is itself unstable, so that's not a problem. And I see no
> sign that GTK+ 4.0 will become stable any time soon.
OK, cool. I wanted to be sure you wouldn't end up with a dependency on
something unstable, but it sounds like that won't be a problem.
___
gtkmm-list mailing list
gtkmm-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtkmm-list
