On Sunday 16 August 2015 11:19:39 Alex Merry wrote:
> On 2015-08-13 09:57, Kai Uwe Broulik wrote:
> > Hi,
> >
> > My experience with MSVC 2013 was that you even need at least Update 4
> > for initializer lists to work properly, which was released quite
> > recently iirc.
>
> And even then, initializer lists don't work in all circumstances
> (specifically in member initialization like
> struct foo {
> int bar[3] = {1, 2, 3};
> };
> ).
>
> Actually, if you do use MSVC 2013, always make sure you install Update
> 4, otherwise the compiler's really quite broken (even generating double
> destructor calls in some circumstances). I don't think it's unreasonable
> to refuse to support MSVC 2013 without update 4.Yep, I know. So can we come to an agreement we would be better off raising the required version to MSVC2013? I feel like people don't really want to revert the C++11 portions of code they've written until now anyway... Cheers, Kevin > Alex > _______________________________________________ > Kde-frameworks-devel mailing list > Kde-frameworks-devel@kde.org > https://mail.kde.org/mailman/listinfo/kde-frameworks-devel -- Kevin Funk | kf...@kde.org | http://kfunk.org
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
