Le 28/09/2015 19:11, Guillaume Munch a écrit :
What about using explicitely lyx::make_shared in the TocBackend code?
Doesn't it solve the ambiguity?
Yes, I can accept this solution given that we won't have to support
c++98 for very long. The drawback is that the issue might pop-up again
in the future if somebody forgets about it because he cannot test
compilation under that other OS. Or maybe it won't compile, but nobody
will notice because nobody cares about c++98 support with msvc now that
c++11 is (supposedly) automatic.
How come that the problem occurs with make_shared, but not shared_ptr,
for example? I see that we use the later without any namespace.
One solution could be to add explicit autoconf-type checks for the
existence of std::make_shared, std::next, etc. This is not difficult,
only a bit tedious.
JMarc
