Re: [Development] Notes on QtCore session @ QCS2016

2016-09-19 Thread Marc Mutz
Can you please move this OT discussion to SG-14 (https://groups.google.com/a/isocpp.org/forum/#!forum/sg14), where it belongs? Thanks, Marc On Friday 16 September 2016 22:43:39 Matthew Woehlke wrote: > I will never, *ever* replace the PRNG shown with a high quality > generator. The use case for

Re: [Development] Notes on QtCore session @ QCS2016

2016-09-16 Thread Matthew Woehlke
On 2016-09-05 20:02, Thiago Macieira wrote: > Em segunda-feira, 5 de setembro de 2016, às 19:00:40 PDT, Giuseppe D'Angelo > escreveu: >> Il 02/09/2016 17:01, Thiago Macieira ha scritto: >>> https://wiki.qt.io/QtCS2016_QtCore >>> >>> * Deprecation of APIs >>> >>> * qrand/qsrand -> replacement

Re: [Development] Notes on QtCore session @ QCS2016

2016-09-06 Thread Thiago Macieira
Em terça-feira, 6 de setembro de 2016, às 17:10:19 PDT, Kevin Kofler escreveu: > Thiago Macieira wrote: > > It was a *choice* not to depend on the C++ Standard Library ABI for > > features outside of the language support. The choice was made during Qt > > 5.0 development, in response to the

Re: [Development] Notes on QtCore session @ QCS2016

2016-09-06 Thread Marc Mutz
Noo don't feed the Troll...! :) -- Marc Mutz | Senior Software Engineer KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company Tel: +49-30-521325470 KDAB - Qt, C++ and OpenGL Experts ___ Development mailing list

Re: [Development] Notes on QtCore session @ QCS2016

2016-09-06 Thread Giuseppe D'Angelo
Il 06/09/2016 17:10, Kevin Kofler ha scritto: > I think it was a mistake to remove -no-stl to begin with, and that Qt API > should not be littered with ugly std:: APIs, not just for ABI reasons, but > also for API (consistency) reasons. Having APIs which follows the naming in the Standard

Re: [Development] Notes on QtCore session @ QCS2016

2016-09-06 Thread Thiago Macieira
Em terça-feira, 6 de setembro de 2016, às 07:24:19 PDT, Marc Mutz escreveu: > On Tuesday 06 September 2016 02:02:50 Thiago Macieira wrote: > > > https://codereview.qt-project.org/#/c/142782/ > > > > We decided to make a QUIP out of this, in a later session. Stay tuned. > > ENOABBREV It's a

Re: [Development] Notes on QtCore session @ QCS2016

2016-09-05 Thread Marc Mutz
On Tuesday 06 September 2016 02:02:50 Thiago Macieira wrote: > > > * C++11 Standard Library compatibility list > > > > > > > > > * no volunteers yet > > > > > > > > Is this a matter of converting this documented into qdoc? > > > > > > > > https://codereview.qt-project.org/#/c/142782/ > >

Re: [Development] Notes on QtCore session @ QCS2016

2016-09-05 Thread Thiago Macieira
Em segunda-feira, 5 de setembro de 2016, às 19:00:40 PDT, Giuseppe D'Angelo escreveu: > Random comments: > > Il 02/09/2016 17:01, Thiago Macieira ha scritto: > > https://wiki.qt.io/QtCS2016_QtCore > > > > * Deprecation of APIs > > > > * qrand/qsrand -> replacement is Standard Library or

Re: [Development] Notes on QtCore session @ QCS2016

2016-09-05 Thread Sune Vuorela
On 2016-09-05, Giuseppe D'Angelo wrote: >> * C++ ABI >> * libstdc++ still breaking compatibility in std::function >> * not now, revisit in a year or two > > There hasn't been time to discuss this at QtCon, but I'd say we should > not spend another year before

Re: [Development] Notes on QtCore session @ QCS2016

2016-09-05 Thread Marc Mutz
On Monday 05 September 2016 19:00:40 Giuseppe D'Angelo wrote: > > * QStringView & QByteArrayView > > > > * Deprecate QStringRef > > * Not QArrayView: discuss later > > IOW: the views will have the full blown QByteArray/QString API on them? The const subset, yes, minus deprecated API, if

Re: [Development] Notes on QtCore session @ QCS2016

2016-09-05 Thread Giuseppe D'Angelo
Random comments: Il 02/09/2016 17:01, Thiago Macieira ha scritto: > https://wiki.qt.io/QtCS2016_QtCore > > * Deprecation of APIs > * qrand/qsrand -> replacement is Standard Library or your own Unfortunately there's no replacement for a thread safe, easy to use, deterministic, low quality