I've seen some blacklists, in the past, that were real flaky tests: things that
would be unstable on any machine, given the proper conditions.
But most of the recent blacklists, and certainly all the BPASS I see when I
run tests, are due to the tests being run in an environment that runs 300x
s
Thiago Macieira wrote:
>> It explains rather unambiguously that clang 3.6 and later set _EXCEPTIONS
>> `if C++ or ObjC exceptions are enabled` and that `To reliably test if C++
>> exceptions are enabled, use _EXCEPTIONS && __has_feature(cxx_exceptions),
>> else things won’t work in all versions o
On Thursday, 25 May 2017 13:32:54 PDT Thiago Macieira wrote:
> We're testing __EXCEPTIONS, like we should.
>
> Please describe the environment in which:
> a) -fno-exceptions is active
> b) __EXCEPTIONS is defined
>
> Provide the full command-line and the compiler version.
>
> I still advise yo
On Thursday, 25 May 2017 12:14:09 PDT René J. V. Bertin wrote:
> Thiago Macieira wrote:
> > It's a bug in your testing, because it sets QT_NO_EXCEPTIONS here with
> > Clang.
> No it's not, ditto for testing by others. In fact, your test is wrong
> because it misses a detail: this concerns ObjC++.
Thiago Macieira wrote:
> It's a bug in your testing, because it sets QT_NO_EXCEPTIONS here with Clang.
No it's not, ditto for testing by others. In fact, your test is wrong because
it
misses a detail: this concerns ObjC++.
See
http://releases.llvm.org/3.6.0/tools/clang/docs/ReleaseNotes.html#
On 25.05.2017 19:03, André Somers wrote:
On 25 May 2017, at 18:40, Christoph Feck wrote:
On 25.05.2017 13:53, André Somers wrote:
Op 25/05/2017 om 12:38 schreef Konstantin Tokarev:
Other problem, that IMO is more serious, is that Qt *requires* user to use
QList,
by returning or taking it as
Hi,
Sent from my phone, please excuse my brevity
> On 25 May 2017, at 18:40, Christoph Feck wrote:
>
>> On 25.05.2017 13:53, André Somers wrote:
>> Op 25/05/2017 om 12:38 schreef Konstantin Tokarev:
>>> Other problem, that IMO is more serious, is that Qt *requires* user to use
>>> QList,
>>> b
On Thursday, 25 May 2017 05:34:59 PDT René J. V. Bertin wrote:
> Hello,
>
> Qglobal.h sets QT_NO_EXCEPTIONS automatically when building with -fno-
> exceptions, but only when a GNU compiler is used, not when using clang. Is
> that an oversight or rather because it's impossible with clang?
It's a
On 25.05.2017 13:53, André Somers wrote:
Op 25/05/2017 om 12:38 schreef Konstantin Tokarev:
Other problem, that IMO is more serious, is that Qt *requires* user to use
QList,
by returning or taking it as and argument in various places. That's almost only
reason why I use QList in my code[*].
If
René J. V. Bertin wrote:
> Hello,
>
> Qglobal.h sets QT_NO_EXCEPTIONS automatically when building with -fno-
> exceptions, but only when a GNU compiler is used, not when using clang. Is
> that an oversight or rather because it's impossible with clang?
The answer is clearly not that it's impossib
Hello,
Qglobal.h sets QT_NO_EXCEPTIONS automatically when building with -fno-
exceptions, but only when a GNU compiler is used, not when using clang. Is that
an oversight or rather because it's impossible with clang?
Curiously this doesn't always lead to errors in template classes that use
QT_T
Op 25/05/2017 om 12:38 schreef Konstantin Tokarev:
>
> 25.05.2017, 02:19, "Ville Voutilainen" :
>> On 24 May 2017 at 22:25, Marc Mutz wrote:
>>> On 2017-05-24 15:12, Konstantin Tokarev wrote:
24.05.2017, 15:49, "NIkolai Marchenko" :
> A semi-sane idea that I think no one has suggeste
25.05.2017, 02:19, "Ville Voutilainen" :
> On 24 May 2017 at 22:25, Marc Mutz wrote:
>> On 2017-05-24 15:12, Konstantin Tokarev wrote:
>>> 24.05.2017, 15:49, "NIkolai Marchenko" :
A semi-sane idea that I think no one has suggested yet:
What if, starting from Qt6, QList becomes
13 matches
Mail list logo
