Re: [Development] QList

On segunda-feira, 27 de março de 2017 15:18:18 PDT Rafael Roquetto wrote: > "“Thrill” > > “Goes back to an old English verb “thryllian” which originally meant pierce. þyrlian - http://bosworth.ff.cuni.cz/032433 þyrelian - http://bosworth.ff.cuni.cz/032427 I used to know a much better

Re: [Development] Proposal to adjust release candidate process

On segunda-feira, 27 de março de 2017 21:21:41 PDT Jani Heikkinen wrote: > > Maybe every week is too aggressive, since few people will test every week > > and give feedback in time for the next release. We may find that every > > other week is better. > > Yes, the goal is to have new beta n about

Re: [Development] QList

On segunda-feira, 27 de março de 2017 14:53:05 PDT Giuseppe D'Angelo wrote: > Why should it bad if what you want return is precisely a "const > reference" over QString-like data? Isn't that the whole reason why we > have functions returning QStringRef right now (lacking a QStringView)? > (And also

Re: [Development] QList

On Monday 27 March 2017 23:53:05 Giuseppe D'Angelo wrote: > Why would > I want to return QStrings for this use case and super-pessimize it? You wouldn't. You can return QStringViews just as well as you can take an iterator into a collection. Whether a give QStringRef return is safe to be

Re: [Development] QList

On Mon, Mar 27, 2017 at 11:47:36AM +, Martin Smith wrote: > > I'm not even counting the argument from authority when > >CS/Math were brought to the table without an invitation > > > I will keep bringing them to the table because, as a documentation guy > following this and other similar

Re: [Development] OT: English phonetic spelling (was: QList)

On Mon, Mar 27, 2017 at 06:44:16PM +0200, Konrad Rosenbaum wrote: > [quite OT, but I'll pile on... - just for fun] > > > Yes, German is almost completely phonetic - except for very few loan words > that have not completely assimilated yet. But there are efforts under way > to send them on an

Re: [Development] QList

Il 27/03/2017 22:56, Thiago Macieira ha scritto: > On segunda-feira, 27 de março de 2017 11:14:24 PDT Giuseppe D'Angelo wrote: >> If we can't make it an alias, can we start adding extra functions for >> the various QStringRef *ref() methods (in QXmlStreamReader, >> QRegularExpressionMatch,

Re: [Development] QList

On segunda-feira, 27 de março de 2017 11:14:24 PDT Giuseppe D'Angelo wrote: > If we can't make it an alias, can we start adding extra functions for > the various QStringRef *ref() methods (in QXmlStreamReader, > QRegularExpressionMatch, probably elsewhere too), returning QStringView? Never return

Re: [Development] QList

On segunda-feira, 27 de março de 2017 12:19:38 PDT Scott Aron Bloom wrote: > My two bits, as a 15+ year Qt professional level user, and semi-active > qt-list person, who is on this list to see whats going on, but doesn’t have > much time to actively develop... Sometimes called a whiner  >

Re: [Development] QList

Il 27/03/2017 21:25, André Pönitz ha scritto: > So that was after the argument of QList being used for a decade by Qt users > was dismissed. > > Good. Sorry, what are we talking about now? The "QList" name, QList as a class/technology, QList usage in Qt public APIs, ...? -- Giuseppe D'Angelo |

Re: [Development] QList

On Mon, Mar 27, 2017 at 09:09:24PM +0200, Giuseppe D'Angelo wrote: > Il 27/03/2017 21:03, André Pönitz ha scritto: > >>> vector is an ordered collection of points, but a QVector can > >>> contain anything; QVector can even contain unlike things, which > >>> is truly a tuple. So the problem

Re: [Development] QList

-Original Message- From: Development [mailto:development-bounces+scott=towel42@qt-project.org] On Behalf Of Giuseppe D'Angelo Sent: Monday, March 27, 2017 12:09 To: André Pönitz Cc: development@qt-project.org Subject: Re: [Development] QList Il 27/03/2017

Re: [Development] QList

Il 27/03/2017 21:03, André Pönitz ha scritto: >>> vector is an ordered collection of points, but a QVector can >>> contain anything; QVector can even contain unlike things, which >>> is truly a tuple. So the problem here is the name QVector. The basic >>> collection should be called QTuple

Re: [Development] QList

Il 27/03/2017 17:46, Thiago Macieira ha scritto: >> Another point that hasn’t been discussed yet, is how to handle QStringRef. >> In my opinion, we should deprecate it, but it’s used quite a bit in some >> parts of our API (QXmlStreamReader comes to my mind). It would be good to >> also think

Re: [Development] OT: English phonetic spelling

On 2017-03-27 12:44, Konrad Rosenbaum wrote: > [quite OT, but I'll pile on... - just for fun] > > On Mon, March 27, 2017 17:43, Matthew Woehlke wrote: >> Iä, thät güst lûks wrå. Yf wi wÿr tu ëvÿr du süch thyz, ai >> wûd müch > > Let me propose the more "Jusfull" "Jäh" - which is somewhat easier

Re: [Development] OT: English phonetic spelling

On 17-03-27 12:44 PM, Konrad Rosenbaum wrote: [quite OT, but I'll pile on... - just for fun] On Mon, March 27, 2017 17:43, Matthew Woehlke wrote: Iä, thät güst lûks wrå. Yf wi wÿr tu ëvÿr du süch thyz, ai wûd müch Let me propose the more "Jusfull" "Jäh" - which is somewhat easier to read.

Re: [Development] OT: English phonetic spelling (was: QList)

[quite OT, but I'll pile on... - just for fun] On Mon, March 27, 2017 17:43, Matthew Woehlke wrote: > Iä, thät güst lûks wrå. Yf wi wÿr tu ëvÿr du süch thyz, ai wûd müch Let me propose the more "Jusfull" "Jäh" - which is somewhat easier to read. > räthÿr swytch holsel tu ü kümplitli fünëtyk

Re: [Development] QList

On segunda-feira, 27 de março de 2017 00:59:58 PDT Lars Knoll wrote: > I am with Marc here. I don’t really see any advantage of inheriting QString > from QStringView. Rather I think it’ll confuse people, even if the > inheritance is private. I guess I will just have to prove that: a) code

[Development] OT: English phonetic spelling (was: QList)

On 2017-03-27 03:43, Marc Mutz wrote: > And "debt" should be spelled "det". It should. It isn't. You can start > writing > det everywhere now, and maybe in a generation you will have collected enough > mindshare that the Oxford Dictionary contains it as an alternative spelling. > Your

Re: [Development] QList

On segunda-feira, 27 de março de 2017 00:22:53 PDT Martin Smith wrote: > QVector should mean QTuple. The name "tuple" has since been repurposed to mean something different. We could go back to Qt 1 name "QArray", but I feel the boat has sailed. -- Thiago Macieira - thiago.macieira (AT)

Re: [Development] QList

> I'm not even counting the argument from authority when >CS/Math were brought to the table without an invitation I will keep bringing them to the table because, as a documentation guy following this and other similar discussions, it looks like you (plural) are willing to ignore the importance

Re: [Development] QList

Il 27/03/2017 13:05, Philippe ha scritto: > QPolygon needs not be a QVector > QPolygon can be a QVector > QPolygon can be a QList ... which confirms the fallacy. > > ...but *today*, QPolygon is "implemented as a QVector" > Hence from the OO common dialect, QPolygon is-a QVector This subthread

Re: [Development] QList

> . points are items > . QPolygon is a sequential collection of points > . QVector is a sequential collection of items > ? QPolygon is-a QVector > > which is a fallacy. QPolygon needs not be a QVector QPolygon can be a QVector QPolygon can be a QList ...but *today*, QPolygon is "implemented as

Re: [Development] QList

>It's also the *fourth* time in a row you're not seeing the paralogism in >your reasoning. >In theory: you're still saying that >. points are items >. QPolygon is a sequential collection of points . QVector is a sequential collection of items >⊢ QPolygon is-a QVector >which is a fallacy. >A

Re: [Development] Proposal to adjust release candidate process

+1 from me to this improved approach -- Tuukka On 27/03/2017, 12.40, "Development on behalf of Jani Heikkinen" wrote: Hi all, Ok, I have thought this now a while & discussed internally

Re: [Development] QList

On 27 Mar 2017, at 10:52, Martin Smith wrote: >> It was about whether QPolygon should inherit QVector, which means >> that a polygon is a vector. That is kind of jolting because people >> don't think of a polygon as being a vector. But back in the day, >> calling a sequential

Re: [Development] first Qt 5.9.0 beta snapshot available

> Hi, > > I see there are Windows snapshots available for the open source builds since > Thursday. Will they also be made available for Enterprise customers? > Yes, hoping already today br, Jani > -Original Message- > From: Development

Re: [Development] Proposal to adjust release candidate process

Hi all, Ok, I have thought this now a while & discussed internally with Tuukka and few others. I have new proposal which is kind of middle between Tuukka's proposal & current process: 1. From FF to beta we will do things as earlier. Of course we need to find ways to cut the time there but it

Re: [Development] QList

> On 27 Mar 2017, at 10:52, Martin Smith wrote: > > It was about whether QPolygon should inherit QVector, which means that a > polygon is a vector. That is kind of jolting because people don't think of a > polygon as being a vector. But back in the day, calling a

Re: [Development] QList

Il 27/03/2017 10:52, Martin Smith ha scritto: >>what's the point of this discussion, anyhow? > > > It was about whether QPolygon should inherit QVector, which means that a > polygon is a vector. That is kind of jolting because people don't think > of a polygon as being a vector. But back in the

Re: [Development] first Qt 5.9.0 beta snapshot available

-Original Message- From: Development [mailto:development-bounces+julius.bullinger=intel@qt-project.org] On Behalf Of Jani Heikkinen Sent: Thursday, March 23, 2017 14:17 To: development@qt-project.org Cc: releas...@qt-project.org Subject: [Development] first Qt 5.9.0 beta snapshot

Re: [Development] P0 Mac help needed due to Daylight savings

On Monday 27 March 2017 10:57:24 Edward Welbourne wrote: > Might I just take this moment to suggest someone review my many (many) > changes to date-time and time-zone code, some of which have languished > for more than a year ? I hadn't caught this one, but some of them fix > this kind of "that

Re: [Development] P0 Mac help needed due to Daylight savings

Thiago Macieira (26 mars 2017 8:12 PM) >> This test began failing today: >> FAIL! : tst_QLocale::macDefaultLocale() >> 'timeString.contains(expectedGMTSpecifier) || >> timeString.contains(expectedGMTSpecifierZeroExtended)' returned FALSE. >> (timeString `1:02:03 AM GMT+02:00',

Re: [Development] QList

>what's the point of this discussion, anyhow? It was about whether QPolygon should inherit QVector, which means that a polygon is a vector. That is kind of jolting because people don't think of a polygon as being a vector. But back in the day, calling a sequential collection of items a vector

Re: [Development] QList

On 24 Mar 2017, at 17:18, Marc Mutz > wrote: On Friday 24 March 2017 16:34:17 Thiago Macieira wrote: Em sexta-feira, 24 de março de 2017, às 01:34:18 PDT, Marc Mutz escreveu: I listed _the_ three use-cases where inheritance is the tool of choice:

Re: [Development] QList

Il 27/03/2017 09:22, Martin Smith ha scritto: > vector is an ordered collection of points, but a QVector can > contain anything; QVector can even contain unlike things, which > is truly a tuple. So the problem here is the name QVector. The basic > collection should be called QTuple or

Re: [Development] QList

On Monday 27 March 2017 09:22:53 Martin Smith wrote: > vector is an ordered collection of points, but a QVector can contain > anything; QVector can even contain unlike things, which is truly a > tuple. So the problem here is the name QVector. The basic collection > should be called QTuple

Re: [Development] RFC: Containers member functions for algorithm

> On Mar 24, 2017, at 10:33 PM, André Pönitz wrote: > > On Fri, Mar 24, 2017 at 04:25:34PM +, Corentin wrote: >> Is std::algo(std::begin(container), std::end(container) ... ) troublesome >> enough that it warrants a wrapper ? > > Yes. > > 1. It is more to read, and

Re: [Development] QList

Op 27/03/2017 om 09:22 schreef Martin Smith: > > > A vector is a collection of points and so is a polygon. Both > are even ordered. > > > vector is an ordered collection of points, but a QVector can > contain anything; QVector can even contain unlike things, which > is truly a tuple. So

Re: [Development] QList

On Monday 27 March 2017 09:22:09 Philippe wrote: > > (the API is lying here, btw: QPainer::drawPolygon(const QPoint *, int) > > suggests that you can manage the storage youself to avoid using the heap. > > But you do that only to have the paint engine create something expensive > > as a

Re: [Development] QList

> A vector is a collection of points and so is a polygon. Both are even ordered. vector is an ordered collection of points, but a QVector can contain anything; QVector can even contain unlike things, which is truly a tuple. So the problem here is the name QVector. The basic collection

Re: [Development] QList

> (the API is lying here, btw: QPainer::drawPolygon(const QPoint *, int) > suggests that you can manage the storage youself to avoid using the heap. But > you do that only to have the paint engine create something expensive as a > QPainterPath first chance it gets). No heap allocation if you

Re: [Development] Qt-5.9.0-beta on CentOS-6.8: one minor BTN_TRIGGER_HAPPY bug

Thanks Thiago, Jani, Kevin. Some testing revealed the 5.8.0 and 5.9.0-beta431 sources all compile and install just fine when given the -no-evdev configure switch, which disables evdev gamepads plugin. So I opened the bug against Packaging and Installation instead: QTBUG-59740. Basically,

Re: [Development] QList

On Sunday 26 March 2017 22:53:59 Martin Smith wrote: > >Yes, using vector for an array type was not Stepanov's best choice of > >terms (he says so himself), but what you're doing is like arguing that > >"debt" should be spelled "det". Yes, it should. No, it isn't. :) > > I disagree, but if we