Re: [Development] Some Qt3D feedback

2015-06-15 Thread Knoll Lars
On 16/06/15 08:14, "André Somers" wrote: >Marc Mutz schreef op 15-6-2015 om 22:26: >> On Monday 15 June 2015 21:01:54 André Pönitz wrote: >>> if so: >>> >>> Please explain how that avoids name clashes. >> You only need to add the prefix when the compiler tells you. E.g. if >>you use >> QtGui

Re: [Development] QtCS: Notes from Modern C++ session

2015-06-15 Thread Koehne Kai
> -Original Message- > From: development-bounces+kai.koehne=theqtcompany.com@qt- > [..] > Depends whether or not we make the choice to break the "no stl in abi" rule. I understood the rule has miniscule practical value, and hinders us from providing the best Qt API possible. So I'm all f

Re: [Development] Some Qt3D feedback

2015-06-15 Thread André Somers
Marc Mutz schreef op 15-6-2015 om 22:26: > On Monday 15 June 2015 21:01:54 André Pönitz wrote: >> if so: >> >> Please explain how that avoids name clashes. > You only need to add the prefix when the compiler tells you. E.g. if you use > QtGui::QTransform in one file and Qt3D::QTransform in ano

Re: [Development] QtCS: Notes from Modern C++ session

2015-06-15 Thread Olivier Goffart
On Monday 15. June 2015 21:30:25 Marc Mutz wrote: > On Monday 15 June 2015 17:43:58 Olivier Goffart wrote: > > On Unix: Clang and GCC build are compatible, > > Yes. > > > C++03/C++11/C++14 builds are compatible. > > No. [... std::list ...] Yes. I was talking about Qt build, and since Qt does no

Re: [Development] QtCS: Notes from Modern C++ session

2015-06-15 Thread Thiago Macieira
On Monday 15 June 2015 13:03:55 Thiago Macieira wrote: > b) Linux distributions that properly compile libc++ [*] > > > > [*] provided, of course, that the two share their base C++ ABI, which > > > some > > > Linux distros have not yet learned to do. By the way, the list of Linux distributions tha

Re: [Development] QtCS: Notes from Modern C++ session

2015-06-15 Thread Thiago Macieira
On Monday 15 June 2015 22:12:46 Marc Mutz wrote: > > I disagree. I understand what you said, but right now it is possible to > > switch from libstdc++ to libc++ with no ill effects[*]. So the question > > is should be asked the other way around: do we knowingly remove this > > currently-working ab

Re: [Development] Some Qt3D feedback

2015-06-15 Thread Marc Mutz
On Monday 15 June 2015 21:01:54 André Pönitz wrote: > if so: > > Please explain how that avoids name clashes. You only need to add the prefix when the compiler tells you. E.g. if you use QtGui::QTransform in one file and Qt3D::QTransform in another, in the same project, you can write QTrans

Re: [Development] QtCS: Notes from Modern C++ session

2015-06-15 Thread Marc Mutz
On Monday 15 June 2015 17:33:35 Thiago Macieira wrote: > On Monday 15 June 2015 17:24:39 Marc Mutz wrote: > > Qt's binary compatibility is between Qt versions, not between toolchains, > > and as such, I don't see a problem saying that if you change the > > toolchain (STL (version)), then the BC gu

Re: [Development] Some Qt3D feedback

2015-06-15 Thread André Pönitz
There seem to be two claims floating around: (a) namespaces help avoiding name clashs -- and -- (b) namespaces are not more onerous than poor man's prefixes I see that that both can be true. I cannot see that both can be true *at the same time*. Which one can be true depends on the recom

Re: [Development] QtCS: Notes from Modern C++ session

2015-06-15 Thread Marc Mutz
On Monday 15 June 2015 17:43:58 Olivier Goffart wrote: > On Unix: Clang and GCC build are compatible, Yes. > C++03/C++11/C++14 builds are > compatible. No. On C++98, std::list is required to have O(1) splice(), in C++11+, O(1) size() instead. The two are mutually exclusive, so std::list cannot

Re: [Development] Specifying module dependencies

2015-06-15 Thread Sergio Ahumada
On 15.06.2015 08:52, Simon Hausmann wrote: > > Perhaps there is a misunderstanding here, so let me confirm also what Joerg > said: At this point we're interested in discussion repository dependencies. I > understand that are somewhat parallel to the qt module dependencies and I > also > unders

Re: [Development] QtCS: Notes from Modern C++ session

2015-06-15 Thread Olivier Goffart
On Monday 15. June 2015 17:24:39 Marc Mutz wrote: > On Monday 15 June 2015 11:49:40 Olivier Goffart wrote: > > On Friday 12. June 2015 14:42:44 Thiago Macieira wrote: > > > On Friday 12 June 2015 18:58:59 Marc Mutz wrote: > > > > On Friday 12 June 2015 16:37:15 Thiago Macieira wrote: > > > > > On F

Re: [Development] QtCS: Notes from Modern C++ session

2015-06-15 Thread Thiago Macieira
On Monday 15 June 2015 17:24:39 Marc Mutz wrote: > Qt's binary compatibility is between Qt versions, not between toolchains, > and as such, I don't see a problem saying that if you change the toolchain > (STL (version)), then the BC guarantees are voided. That's just what we > have now already. I

Re: [Development] Some Qt3D feedback

2015-06-15 Thread Thiago Macieira
On Monday 15 June 2015 13:01:04 Sean Harmer wrote: > * The existing syncqt.pl works syncqt actually has support for namespaces so you could #include but I think it's disabled since it has some bugs and nothing is using it. We could re-enable it. Note that the namespace should not be the same a

Re: [Development] QtCS: Notes from Modern C++ session

2015-06-15 Thread Marc Mutz
On Monday 15 June 2015 11:49:40 Olivier Goffart wrote: > On Friday 12. June 2015 14:42:44 Thiago Macieira wrote: > > On Friday 12 June 2015 18:58:59 Marc Mutz wrote: > > > On Friday 12 June 2015 16:37:15 Thiago Macieira wrote: > > > > On Friday 12 June 2015 12:12:17 Olivier Goffart wrote: > > > > >

Re: [Development] Some Qt3D feedback

2015-06-15 Thread Knoll Lars
On 12/06/15 16:59, "development-bounces+lars.knoll=theqtcompany@qt-project.org on behalf of Sean Harmer" wrote: >Thanks for structuring this! Much appreciated. > >On Friday 12 June 2015 22:23:09 Sze Howe Koh wrote: >> First, a big thanks to Stephen for bringing the >> I propose the followi

Re: [Development] Some Qt3D feedback

2015-06-15 Thread Sean Harmer
On 15/06/2015 12:49, Knoll Lars wrote: > On 15/06/15 12:27, > "development-bounces+lars.knoll=theqtcompany@qt-project.org on behalf of > Simon Hausmann" > simon.hausm...@theqtcompany.com> wrote: > >> On Monday, June 15, 2015 10:18:38 AM Marc Mutz wrote: >> [...] > QtConcurrent A na

Re: [Development] Some Qt3D feedback

2015-06-15 Thread Knoll Lars
On 15/06/15 12:27, "development-bounces+lars.knoll=theqtcompany@qt-project.org on behalf of Simon Hausmann" wrote: >On Monday, June 15, 2015 10:18:38 AM Marc Mutz wrote: >[...] >> > > QtConcurrent >> > >> > A namespace for functions only, no public classes within. >> > >> > > QTest >> >

Re: [Development] Some Qt3D feedback

2015-06-15 Thread Simon Hausmann
On Monday, June 15, 2015 10:18:38 AM Marc Mutz wrote: [...] > > > QtConcurrent > > > > A namespace for functions only, no public classes within. > > > > > QTest > > > > A namespace for functions only, no public classes within. > > _That_ argument again... :) > > Could you explain to me why you

Re: [Development] QtCS: Notes from Modern C++ session

2015-06-15 Thread Olivier Goffart
On Friday 12. June 2015 14:42:44 Thiago Macieira wrote: > On Friday 12 June 2015 18:58:59 Marc Mutz wrote: > > On Friday 12 June 2015 16:37:15 Thiago Macieira wrote: > > > On Friday 12 June 2015 12:12:17 Olivier Goffart wrote: > > > > Which mean using things like std::function, std::unique_ptr, in

Re: [Development] Some Qt3D feedback

2015-06-15 Thread Marc Mutz
On Monday 15 June 2015 08:24:22 Simon Hausmann wrote: > > QtPatternist > > An internal namespace, not reflected in the public API. QtPatternist::Item appears in public functions of exported public API class QXmlNodeModelIndex, e.g. Yes, now I see the comment (git grep hid it). > > QtConcurrent >