On Mon, 05 Nov 2018 14:41:11 +0100, Giuseppe D'Angelo via Interest wrote:
> Didn't you hear from Microsoft? They went from being the
> slowest adopter to the fastest -- to this date, MSVC 2017.7 is the
> _only_ C++ compiler that supports the entirety of C++17! That indeed
> shows their
Hi,
On 04/11/2018 00:07, Roland Hughes wrote:
Giuseppe,
I missed the beginning of this thread and don't have enough time for one
of my usual missives. I did want to take issue with the comment about
using C++ latest.
It's _never_ a good idea to chase a standard.
[citation needed], I'm
Il 02/11/18 19:28, Jason H ha scritto:
The bitwise OR operator, descending multiple namespaces.
It makes my point. That these very common functional programming paradigms
(map, reduce, etc) are (needlessly?) obtuse in C++.
Sorry, what is the point? Is it hard to read, write, teach, learn,
Giuseppe,
I missed the beginning of this thread and don't have enough time for one
of my usual missives. I did want to take issue with the comment about
using C++ latest.
It's _never_ a good idea to chase a standard.
Please allow a few words of caution from a grizzled old code warrior.
I
> > The bitwise OR operator, descending multiple namespaces.
> > It makes my point. That these very common functional programming paradigms
> > (map, reduce, etc) are (needlessly?) obtuse in C++.
>
> Sorry, what is the point? Is it hard to read, write, teach, learn,
> understand, extend...?
Hi,
Il 01/11/18 21:14, Jason H ha scritto:
originals | ranges::view::transform([](int i) { return i * 3; });
The bitwise OR operator, descending multiple namespaces.
It makes my point. That these very common functional programming paradigms
(map, reduce, etc) are (needlessly?) obtuse in C++.
> Sent: Thursday, November 01, 2018 at 3:44 PM
> From: "Giuseppe D'Angelo"
> To: "Jason H"
> Cc: interest@qt-project.org
> Subject: Re: [Interest] Qt API annoyances: where to log/discuss?
>
> Il 31/10/18 21:59, Jason H ha scritto:
> > Tha
Il 31/10/18 21:59, Jason H ha scritto:
Thanks Giuseppe! That's getting closer :-) however the expression boggles my mind. "originals | ranges::view::transform" there's a lot of compiler voodoo there. I'm trying to keep up on all the C++0xYZ developments, and still trying to wrap my head around
> To: "Jason H" , "giuseppe.dang...@kdab.com"
>
> Cc: "interest@qt-project.org"
> Subject: RE: [Interest] Qt API annoyances: where to log/discuss?
>
> All those back_inserter() and C++0xXY template make our life easier in the
> end, I
: interest@qt-project.org
Subject: Re: [Interest] Qt API annoyances: where to log/discuss?
> Sent: Wednesday, October 31, 2018 at 4:30 PM
> From: "Giuseppe D'Angelo via Interest"
> To: interest@qt-project.org
> Subject: Re: [Interest] Qt API annoyances: where to log/discuss?
>
&
> Sent: Wednesday, October 31, 2018 at 4:30 PM
> From: "Giuseppe D'Angelo via Interest"
> To: interest@qt-project.org
> Subject: Re: [Interest] Qt API annoyances: where to log/discuss?
>
> Il 31/10/18 18:35, Jason H ha scritto:
> > I attempted this recently,
> Sent: Wednesday, October 31, 2018 at 3:42 PM
> From: "Elvis Stansvik"
> To: "Jason H"
> Cc: "Thiago Macieira" , "interest@qt-project.org
> Interest"
> Subject: Re: [Interest] Qt API annoyances: where to log/discuss?
>
>
Il 31/10/18 18:35, Jason H ha scritto:
I attempted this recently, but failed to figure out how to do the following:
QVector triple = apply(QVector {1,2,3},[](item) { return item*3;});
or
QVector originals {1,2,3};
QVector triples = originals.apply([](item) { return item*3;});
You do this:
Den ons 31 okt. 2018 kl 18:35 skrev Jason H :
>
>
>
> > Sent: Tuesday, October 30, 2018 at 3:23 PM
> > From: "Thiago Macieira"
> > To: interest@qt-project.org
> > Subject: Re: [Interest] Qt API annoyances: where to log/discuss?
> >
> >
On Wednesday, 31 October 2018 10:35:15 PDT Jason H wrote:
> > That's because QUrl::port() can return -1, indicating "no port was set in
> > the URL". QTcpServer needs a valid port number. So the warning is correct
> > and should be acted on.
>
> I thought QUrl::port() can take a default port if
> Sent: Tuesday, October 30, 2018 at 3:23 PM
> From: "Thiago Macieira"
> To: interest@qt-project.org
> Subject: Re: [Interest] Qt API annoyances: where to log/discuss?
>
> On Tuesday, 30 October 2018 08:39:22 PDT Jason H wrote:
> > I was wondering if there is
On Tuesday, 30 October 2018 08:39:22 PDT Jason H wrote:
> I was wondering if there is a place to log annoyances/discuss with the Qt5
> API for fix in Qt6?
This list or the development mailing list are fine.
>
> Two I am thinking of right now is:
> - QUrl::port() returns an int, but QTcpServer
On Tue, Oct 30, 2018 at 5:39 PM Jason H wrote:
> I was wondering if there is a place to log annoyances/discuss with the Qt5
> API for fix in Qt6?
>
Probably a good idea is to submit a suggestion to the bugtracker as well.
Two I am thinking of right now is:
> - QUrl::port() returns an int, but
18 matches
Mail list logo
