On Friday 28 October 2016 14:31:39 Иван Комиссаров wrote:
> But is's not fixed yet?
I didn't look into C++17, but I'd be surprised if it was changed in std. I'd
expect such a change in std2, when it happens.
Thanks,
Marc
> 2016-10-28 14:14 GMT+03:00 Marc Mutz :
> > They are. It took two decade
But is's not fixed yet?
2016-10-28 14:14 GMT+03:00 Marc Mutz :
>
> They are. It took two decades for this bug to be noticed, and while it
> should
> be fixed, in std2, probably, code that relies on either behaviour must atm
> be
> considered buggy.
>
__
On Thursday 27 October 2016 22:54:16 Kevin Kofler wrote:
> Marc Mutz wrote:
> > And, again, by proprietarily extending a perfectly adequate std
> > functionality, we lock ourselves deeper into our NIHS, losing new
> > functionality provided by newer std versions, in this case: variadic
> > std::min
Marc Mutz wrote:
> And, again, by proprietarily extending a perfectly adequate std
> functionality, we lock ourselves deeper into our NIHS, losing new
> functionality provided by newer std versions, in this case: variadic
> std::min/max.
So once again you want to artificially restrict what Qt does
Sergio Martins wrote:
> The real issue understanding is "why don't users contribute trivial
> changes that they need".
>
> You see it all the time:
>
> - users complaining on a JIRA bug for 2 years instead of submitting a
> one-liner
> - users reporting wiki typo instead of editing wiki
> - users
On quinta-feira, 27 de outubro de 2016 09:50:00 PDT Marc Mutz wrote:
> (for equivalent elements, min() should returnt
> the one max() does not, which IIRC qMin()/qMax() do, but, notably,
> std::min/max do not, unless they changed it in C++14+).
If they're equal, they're equal. Making a distinction
On Thursday 27 October 2016 08:41:19 Thiago Macieira wrote:
> On quinta-feira, 27 de outubro de 2016 08:23:57 PDT Marc Mutz wrote:
> > And, again, by proprietarily extending a perfectly adequate std
> > functionality, we lock ourselves deeper into our NIHS, losing new
> > functionality provided by
On quinta-feira, 27 de outubro de 2016 08:23:57 PDT Marc Mutz wrote:
> And, again, by proprietarily extending a perfectly adequate std
> functionality, we lock ourselves deeper into our NIHS, losing new
> functionality provided by newer std versions, in this case: variadic
> std::min/max.
Hm... yo
> Am 27.10.2016 um 08:23 schrieb Marc Mutz :
>
>> On Thursday 27 October 2016 01:23:15 Thiago Macieira wrote:
>> On quinta-feira, 27 de outubro de 2016 00:49:21 PDT Ola Røer Thorsen wrote:
https://codereview.qt-project.org/175025
>>>
>>> That's sort of a "sledge hammer" fix. Wouldn't this ma
On Thursday 27 October 2016 01:23:15 Thiago Macieira wrote:
> On quinta-feira, 27 de outubro de 2016 00:49:21 PDT Ola Røer Thorsen wrote:
> > > https://codereview.qt-project.org/175025
> >
> > That's sort of a "sledge hammer" fix. Wouldn't this make it easier to be
> > careless about mixing floats
On quinta-feira, 27 de outubro de 2016 00:49:21 PDT Ola Røer Thorsen wrote:
> > https://codereview.qt-project.org/175025
>
> That's sort of a "sledge hammer" fix. Wouldn't this make it easier to be
> careless about mixing floats and doubles? I think it's a good practice to
> avoid mixing when poss
2016-10-26 23:20 GMT+02:00 Thiago Macieira :
> On quarta-feira, 26 de outubro de 2016 17:40:52 PDT Sergio Martins wrote:
> > That's not enough and probably just 10% of the cost of the solution. One
> > also needs to figure the contribution process and commit. The problem
> > here is not technical,
On quarta-feira, 26 de outubro de 2016 17:40:52 PDT Sergio Martins wrote:
> On 2016-10-26 16:01, Thiago Macieira wrote:
> > On quarta-feira, 26 de outubro de 2016 10:18:49 PDT Ola Røer Thorsen
> >
> > wrote:
> >> I'm getting compile errors building both Qt 5.6.2 and 5.8 beta from
> >> source
> >>
On 2016-10-26 16:01, Thiago Macieira wrote:
On quarta-feira, 26 de outubro de 2016 10:18:49 PDT Ola Røer Thorsen
wrote:
I'm getting compile errors building both Qt 5.6.2 and 5.8 beta from
source
when configuring Qt with -qreal float and building using g++ on Linux.
The
affected modules are Cha
On quarta-feira, 26 de outubro de 2016 10:18:49 PDT Ola Røer Thorsen wrote:
> I'm getting compile errors building both Qt 5.6.2 and 5.8 beta from source
> when configuring Qt with -qreal float and building using g++ on Linux. The
> affected modules are Charts and Location.
>
> https://bugreports.q
I'm getting compile errors building both Qt 5.6.2 and 5.8 beta from source
when configuring Qt with -qreal float and building using g++ on Linux. The
affected modules are Charts and Location.
https://bugreports.qt.io/browse/QTBUG-56715
I would think that this should be given a higher priority tha
16 matches
Mail list logo
