On quinta-feira, 24 de outubro de 2013 17:53:24, Thiago Macieira wrote:
> [erase text I had written]
>
> After writing an example, I realise that there is a solution and it's the
> same I'm implementing for GCC: we need the qstring_compat.cpp (for
> example) that I added in
> https://code
On quinta-feira, 24 de outubro de 2013 17:42:01, Olivier Goffart wrote:
> On Thursday 24 October 2013 14:49:39 Thiago Macieira wrote:
> > Hello
> >
> > I'm going to add an #error to qcompilerdetection.h for any unreleased
> > version of MSVC.
>
> I am opposed to that.
>
> Can I do the same for a
On Thursday 24 October 2013 14:49:39 Thiago Macieira wrote:
> Hello
>
> I'm going to add an #error to qcompilerdetection.h for any unreleased
> version of MSVC.
I am opposed to that.
Can I do the same for any unreleased version of ICC?
And a qFatal if it Qt runs on any unreleased CPU?
> The r
t: Thursday, October 24, 2013 4:39 PM
>> To: development@qt-project.org
>> Subject: Re: [Development] #error for unreleased MSVC versions
>>
>> On quinta-feira, 24 de outubro de 2013 16:09:37, Yves Bailly wrote:
>> > While I understand the reasoning about binary compa
If it's a configure option, we should note if this was done in the
binary so that we can know to ignore the inevitable bug reports.
Rich.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
ect: Re: [Development] #error for unreleased MSVC versions
>
> On quinta-feira, 24 de outubro de 2013 16:09:37, Yves Bailly wrote:
> > While I understand the reasoning about binary compatibility, in my
> > humble opinion such a drastic change should be at least deactivable,
> >
On quinta-feira, 24 de outubro de 2013 16:09:37, Yves Bailly wrote:
> While I understand the reasoning about binary compatibility, in my humble
> opinion such a drastic change should be at least deactivable, for example
> by adding a switch to "configure", something like
> "-ignore-binary-compatibi
On quinta-feira, 24 de outubro de 2013 13:55:42, Poenitz Andre wrote:
> Am I understanding this right that this will make such versions of Qt
> uncompilable _even for people who do not care about binary compatibility_?
Yes. I do plan on making #error message include information on how you can get
Hello,
Le 24/10/2013 15:49, Thiago Macieira a écrit :
> I'm going to add an #error to qcompilerdetection.h for any unreleased version
> of MSVC.
> The reason is this combination:
> 1) MSVC does not provide a way to turn C++11 off (and won't provide for C++14
> either)
> 2) MSVC does instantiates *
Thiago Macieira [thiago.macie...@intel.com]
> I'm going to add an #error to qcompilerdetection.h for any unreleased version
> of MSVC.
>
> ==> In other words, adding new Q_COMPILER_xxx defines for C++11 for MSVC
> breaks
>binary compatibility <===
>
> For that reason and because we don'
Hello
I'm going to add an #error to qcompilerdetection.h for any unreleased version
of MSVC.
The reason is this combination:
1) MSVC does not provide a way to turn C++11 off (and won't provide for C++14
either)
2) MSVC does instantiates *ALL* class members of exported classes, even inline
f
11 matches
Mail list logo
