Re: [Development] Proposal: adding Q_DECL_NOEXCEPT to many methods

On quinta-feira, 2 de agosto de 2012 23.57.58, Marc Mutz wrote: > noexcept(std::declval().f()) should work. Unfortunately, while the C++11 compiler support seems to be going fine, the library support is lagging WAY behind. Add to that the fact that some compilers are being used with incompatible

Re: [Development] Proposal: adding Q_DECL_NOEXCEPT to many methods

On sexta-feira, 3 de agosto de 2012, às 00.25.04, you wrote: > AFAIU, the compiler needs to make sure that std::terminate is called if an > unexpected exception is thrown, which would require the equivalent of a > function-try-catch block where the catch block calls std::terminate(). > > Do you hav

Re: [Development] Proposal: adding Q_DECL_NOEXCEPT to many methods

Hi Thiago, On Thursday August 2 2012, Thiago Macieira wrote: > The benefits are: >  - callers do not need to emit exception handlers around such functions >  - the compiler may assume that no exception unexpectedly happens inside > that function body, foregoing exception handlers inside it as well

Re: [Development] Proposal: adding Q_DECL_NOEXCEPT to many methods

On Thursday August 2 2012, Thiago Macieira wrote: > On quinta-feira, 2 de agosto de 2012 16.02.43, Marc Mutz wrote: [] > By the way, I'm running into an issue which I'm not entirely sure whether > it's a design issue. Imagine this case: > > class Object > { > void f(); > void g() noexce

Re: [Development] Proposal: adding Q_DECL_NOEXCEPT to many methods

On Thursday August 2 2012, Konrad Rosenbaum wrote: > On Thursday 02 August 2012, Thiago Macieira wrote: > > On quinta-feira, 2 de agosto de 2012 17.55.54, Konrad Rosenbaum wrote: > > > Where is qHash(QDateTime) defined? It doesn't seem to be where I > > > expected it (qhash.* or qdatetime.*). > > >

Re: [Development] state of Qt's Australia office

On 02/08/2012, at 10:02 PM, wrote: > I talked a bit with the team in Brisbane this morning. Obviously the mood > there is somewhat grim. Grim yes, but at least we now know what is happening with our jobs in respect to Nokia. > > Talking for me, it's really sad to see this happen. There ar

Re: [Development] Proposal: adding Q_DECL_NOEXCEPT to many methods

On quinta-feira, 2 de agosto de 2012 19.47.46, marius.storm-ol...@nokia.com wrote: > This tells me that MSVC's implementation of throw() == noexcept(true) > for all intents and purposes, and we can use that in Qt. Ah, that changes everything. But we can just use __declspec(nothrow) then, to be on

Re: [Development] Proposal: adding Q_DECL_NOEXCEPT to many methods

On quinta-feira, 2 de agosto de 2012 19.25.31, marius.storm-ol...@nokia.com wrote: > Anyways, I see that LLVM/libc++ > (http://llvm.org/svn/llvm-project/libcxx/trunk/include/__config) defines > it like this: >#if (__has_feature(cxx_noexcept)) ># define _NOEXCEPT noexcept ># define _NO

Re: [Development] Proposal: adding Q_DECL_NOEXCEPT to many methods

On Thursday 02 August 2012, Thiago Macieira wrote: > On quinta-feira, 2 de agosto de 2012 17.55.54, Konrad Rosenbaum wrote: > > Where is qHash(QDateTime) defined? It doesn't seem to be where I > > expected it (qhash.* or qdatetime.*). > > qdatetime.{h,cpp} Ok, found it - had the wrong branch chec

Re: [Development] Proposal: adding Q_DECL_NOEXCEPT to many methods

On 02/08/2012 14:25, ext marius.storm-ol...@nokia.com wrote: > On 02/08/2012 12:55, ext Thiago Macieira wrote: >> On quinta-feira, 2 de agosto de 2012 17.32.36, >> marius.storm-ol...@nokia.com wrote: >>> "the compiler can eliminate the mechanics of tracking the >>> lifetime of certain unwindable ob

Re: [Development] Proposal: adding Q_DECL_NOEXCEPT to many methods

On 02/08/2012 12:55, ext Thiago Macieira wrote: > On quinta-feira, 2 de agosto de 2012 17.32.36, > marius.storm-ol...@nokia.com wrote: >> "the compiler can eliminate the mechanics of tracking the lifetime >> of certain unwindable objects in such a function, and significantly >> reduce the code size

Re: [Development] Proposal: adding Q_DECL_NOEXCEPT to many methods

On quinta-feira, 2 de agosto de 2012 17.32.36, marius.storm-ol...@nokia.com wrote: > "the compiler can eliminate the mechanics of tracking the lifetime of > certain unwindable objects in such a function, and significantly reduce > the code size". That's in the caller. The problem is in the callee

Re: [Development] Proposal: adding Q_DECL_NOEXCEPT to many methods

On 02/08/2012 12:39, ext marius.storm-ol...@nokia.com wrote: > On 02/08/2012 12:32, ext marius.storm-ol...@nokia.com wrote: >> On 02/08/2012 12:19, ext Thiago Macieira wrote: >>> On quinta-feira, 2 de agosto de 2012 17.15.26, marius.storm-ol...@nokia.com >>> wrote: So, perhaps we can identify

Re: [Development] Proposal: adding Q_DECL_NOEXCEPT to many methods

On 02/08/2012 12:32, ext marius.storm-ol...@nokia.com wrote: > On 02/08/2012 12:19, ext Thiago Macieira wrote: >> On quinta-feira, 2 de agosto de 2012 17.15.26, marius.storm-ol...@nokia.com >> wrote: >>> So, perhaps we can identify the cases where they are similar and use >>> that with MSVC until p

Re: [Development] Proposal: adding Q_DECL_NOEXCEPT to many methods

On 02/08/2012 12:19, ext Thiago Macieira wrote: > On quinta-feira, 2 de agosto de 2012 17.15.26, marius.storm-ol...@nokia.com > wrote: >> So, perhaps we can identify the cases where they are similar and use >> that with MSVC until proper noexcept()/noexcept() support is provided? > > Yes. I can ide

Re: [Development] Proposal: adding Q_DECL_NOEXCEPT to many methods

On quinta-feira, 2 de agosto de 2012 17.15.26, marius.storm-ol...@nokia.com wrote: > So, perhaps we can identify the cases where they are similar and use > that with MSVC until proper noexcept()/noexcept() support is provided? Yes. I can identify where they are similar: nowhere. If you add it,

Re: [Development] Proposal: adding Q_DECL_NOEXCEPT to many methods

On 02/08/2012 07:50, ext Thiago Macieira wrote: > The macro expands to nothing in C++98 mode. That means code using the > API so marked and compiling in C++98 mode will simply not gain the > benefits of the keyword, but should see no side effects. > > The presence of the keyword does not affect bin

Re: [Development] Proposal: adding Q_DECL_NOEXCEPT to many methods

On quinta-feira, 2 de agosto de 2012 17.55.54, Konrad Rosenbaum wrote: > Hi, > > On Thursday 02 August 2012 15:27:03 Thiago Macieira wrote: > > For example, in when I was just now adding it to qHash for QDateTime, I > > realised it does complex operations. Right now, none of those operations > > al

Re: [Development] Proposal: adding Q_DECL_NOEXCEPT to many methods

Hi, On Thursday 02 August 2012 15:27:03 Thiago Macieira wrote: > For example, in when I was just now adding it to qHash for QDateTime, I > realised it does complex operations. Right now, none of those operations > allocate memory, but it's actually very close to doing that. QDateTime has > a d poi

Re: [Development] Can we have id's in dynamically generated elements for the next QML?

> > But i still don't fully understand how to make a component draggable > when it's being created dynamically through a Repeater.. Don't you > just need an id for that to work? You can use the delegate id to do the dragging. Take a look in this [1] example, maybe it fits for your case. [1] - ht

Re: [Development] state of Qt's Australia office

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 02.08.2012 14:56, schrieb Thiago Macieira: > On quinta-feira, 2 de agosto de 2012 15.48.19, a.gra...@gmail.com > wrote: >> 2) RIM must patch upstream any improvement and Qt will benefit >> from this > > I'm not sure if you meant "upstream" in the w

Re: [Development] Can we have id's in dynamically generated elements for the next QML?

On Thu, Aug 2, 2012 at 4:29 AM, Alan Alpert wrote: > On Wed, 1 Aug 2012 12:59:08 ext Charley Bay wrote: >> Mark spaketh: >> > Sadly, QML 1 doesn't have id in dynamically generated id. That is a >> > real big pain if you want to drag/drop something since then you >> > need... an id! Right now i'm

Re: [Development] Proposal: adding Q_DECL_NOEXCEPT to many methods

On quinta-feira, 2 de agosto de 2012 16.02.43, Marc Mutz wrote: > Need to be careful with templates. Can't use add the unrestricted noexcept > there, need to use noexcept(noexcept(expr)), which is even uglier template inline uint qHash(const T &t, uint seed) Q_DECL_NOEXCEPT_EXPR(noexcept(qHash

Re: [Development] Proposal: adding Q_DECL_NOEXCEPT to many methods

Hi Thiago, On Thursday August 2 2012, Thiago Macieira wrote: > I'd like to propose we add Q_DECL_NOEXCEPT to many methods in our API. +1 from me, too. [Though it doesn't seem to help with the problem that move constructors can't be inline if the class uses smart pointers. It still wants to call

Re: [Development] Proposal: adding Q_DECL_NOEXCEPT to many methods

On quinta-feira, 2 de agosto de 2012 13.00.22, lars.kn...@nokia.com wrote: > I'd say go ahead. Since adding it shouldn't change the ABI/name mangling, we > can introduce this gradually anyway. By the way, let's be conservative instead of doing it throughout. Once added, the noexcept keyword canno

Re: [Development] Proposal: adding Q_DECL_NOEXCEPT to many methods

Thiago spaketh: > I'd like to propose we add Q_DECL_NOEXCEPT to many methods in our API. > > We already took the decision to turn exception off in most modules, except > QtCore and where exceptions were used, like QtXmlPatterns. This is the next > step. > > The Q_DECL_NOEXCEPT macro expands to noe

Re: [Development] state of Qt's Australia office

On 2 August 2012 15:56, Thiago Macieira wrote: > On quinta-feira, 2 de agosto de 2012 15.48.19, a.gra...@gmail.com wrote: >> 2) RIM must patch upstream any improvement and Qt will benefit from this > > I'm not sure if you meant "upstream" in the way that I understand it. So let's > be clear: > > A

Re: [Development] Proposal: adding Q_DECL_NOEXCEPT to many methods

I'd say go ahead. Since adding it shouldn't change the ABI/name mangling, we can introduce this gradually anyway. Cheers, Lars On Aug 2, 2012, at 2:50 PM, ext Thiago Macieira wrote: > I'd like to propose we add Q_DECL_NOEXCEPT to many methods in our API. > > We already took the decision to t

Re: [Development] Qt Essentials

On quinta-feira, 2 de agosto de 2012 14.39.02, Yves Bailly wrote: > For what is worthes, here we're hardly waiting for Qt3D, delaying an > internal long-term project which would have been quite similar. That said > we're not the ones doing the job on Qt3D, so any decision you make will be > seen as

Re: [Development] state of Qt's Australia office

On quinta-feira, 2 de agosto de 2012 15.48.19, a.gra...@gmail.com wrote: > 2) RIM must patch upstream any improvement and Qt will benefit from this I'm not sure if you meant "upstream" in the way that I understand it. So let's be clear: Any user of LGPL must make their modifications available to

Re: [Development] state of Qt's Australia office

Hi, On 2 August 2012 15:36, Peter Rullmann wrote: > On Wed, 01 Aug 2012 17:02:14 +0200, C. Bergström > wrote: >> For the companies reading this (RIM) - step up and post a job to get >> this thread back on track. > > We do have a job open for a skilled Qt and QML platform developer. > It is in Ge

Re: [Development] qsrand(31415) int qt3d

* Done: Qt/ QTBUG-26744 Best regards Helmut Von: mitch.cur...@nokia.com [mailto:mitch.cur...@nokia.com] Gesendet: Donnerstag, 02. August 2012 14:46 An: Mülner, Helmut Betreff: RE: qsrand(3141

Re: [Development] state of Qt's Australia office

On quinta-feira, 2 de agosto de 2012 15.23.06, a.gra...@gmail.com wrote: > On 2 August 2012 15:15, Dmytro Poplavskiy wrote: > > It's possible to use LGPL Qt in the commercial products, > > it's only necessary to open changes done to the Qt itself if any. > > I will try to be more specific with my

[Development] Proposal: adding Q_DECL_NOEXCEPT to many methods

I'd like to propose we add Q_DECL_NOEXCEPT to many methods in our API. We already took the decision to turn exception off in most modules, except QtCore and where exceptions were used, like QtXmlPatterns. This is the next step. The Q_DECL_NOEXCEPT macro expands to noexcept, which is a new C++11

Re: [Development] Qt Essentials

same feeling about QT3D : we can't compare QT3D Feature to for example ogre3D, but for simple things I use Qt3D since two years and it works fine for all my needs ... without bugs 2012/8/2 Charley Bay > Agree with Thiago: > > For 3D and Location, I have a feeling it's a little premature, but I

Re: [Development] state of Qt's Australia office

Hi, On 2 August 2012 15:40, Rafael Roquetto wrote: > RIM is using Qt open source (LGPL). so happy for this :) I'm happy because: 1) RIM is able to continue using Qt without any restriction 2) RIM must patch upstream any improvement and Qt will benefit from this > To be really honest, generally

Re: [Development] state of Qt's Australia office

On Thu, Aug 02, 2012 at 03:23:06PM +0300, a.gra...@gmail.com wrote: > On 2 August 2012 15:15, Dmytro Poplavskiy wrote: > > It's possible to use LGPL Qt in the commercial products, > > it's only necessary to open changes done to the Qt itself if any. > > I will try to be more specific with my ques

Re: [Development] Qt Essentials

Agree with Thiago: For 3D and Location, I have a feeling it's a little premature, but I can't > blame you for it. Especially in Location's case, with lots of plugins to be > kept in working order, it might be tricky in the current situation. > > Qt3D might be quite mature, actually, since it's bee

Re: [Development] Qt Essentials

Greetings all, first of all let me express a deep and warm feeling for all those writing so nice code since so long and "rewarded" in such manner... Le 02/08/2012 14:26, Thiago Macieira a écrit : > [...] > > Qt3D might be quite mature, actually, since it's been around for longer and > has no plat

Re: [Development] state of Qt's Australia office

On Wed, 01 Aug 2012 17:02:14 +0200, C. Bergström wrote: > For the companies reading this (RIM) - step up and post a job to get > this thread back on track. We do have a job open for a skilled Qt and QML platform developer. It is in Germany though: https://barco.taleo.net/careersection/2/jobdeta

[Development] qsrand(31415) int qt3d

I already sent this to the qt3d mailing list, but nobody reacts on this list (maybe due to the Bisbane situation): qglsection.cpp contains the following lines in the method QGLSectionPrivate::mapVertex: static bool seeded = false; if (!seeded) qsrand(31415); This ma

Re: [Development] Qt Essentials

On quinta-feira, 2 de agosto de 2012 12.02.45, lars.kn...@nokia.com wrote: > Hi everybody, > > as one of the first consequences of the situation in Brisbane, I'd like to > do some changes to our list of essential modules. You can see the current > list at http://qt-project.org/wiki/Qt-Essentials-Mo

Re: [Development] state of Qt's Australia office

On 2 August 2012 15:15, Dmytro Poplavskiy wrote: > It's possible to use LGPL Qt in the commercial products, > it's only necessary to open changes done to the Qt itself if any. I will try to be more specific with my question :) What kind of license is using RIM for their Cascades UI? It's based o

Re: [Development] Can we have id's in dynamically generated elements for the next QML?

Thanks, Alan -- very rich email that helps me think about declarative-model-instance-handling. Alan spaketh: > Reusable components/delegates, where data propagates in one direction, is > the > best-practices pattern that obviates this need. , > For list delegates, this is managed through the m

Re: [Development] state of Qt's Australia office

On Thu, Aug 2, 2012 at 10:09 PM, a.gra...@gmail.com wrote: > Hi, > > On 2 August 2012 15:02, wrote: >> For Qt as a product, it is now really important to remember that we do have >> the Qt project and a live and active community around it. This might make >> some things a bit more difficult in t

Re: [Development] state of Qt's Australia office

Hi, On 2 August 2012 15:02, wrote: > For Qt as a product, it is now really important to remember that we do have > the Qt project and a live and active community around it. This might make > some things a bit more difficult in the short term, but we will find ways to > deal with this and to cont

Re: [Development] state of Qt's Australia office

I talked a bit with the team in Brisbane this morning. Obviously the mood there is somewhat grim. Talking for me, it's really sad to see this happen. There are a lot of bright engineers working in that office and I have been working with many of them for quite some time now. I really hope that

Re: [Development] state of Qt's Australia office

I talked a bit with the team in Brisbane this morning. Obviously the mood there is somewhat grim. Talking for me, it's really sad to see this happen. There are a lot of bright engineers working in that office and I have been working with many of them for quite some time now. I really hope that

[Development] Qt Essentials

Hi everybody, as one of the first consequences of the situation in Brisbane, I'd like to do some changes to our list of essential modules. You can see the current list at http://qt-project.org/wiki/Qt-Essentials-Modules . I intend to move both Qt 3D and Qt Location out of the essentials list a

Re: [Development] Color Profile support on Qt

I reverted the patch as requested. The change id is : Ic4a420d6ad0995810ed61d31edd28e7b603cca5e I also created a clone of qtbase repository on gitorious. the link for that is https://qt.gitorious.org/~alexandrosdermenakis/qt/qtbase-colorprofiles Alex Fro

Re: [Development] QtGui depends on libPlatformSupport.a

QtGui should not depend on platform support. If it does it's a bug. Cheers, Lars On Aug 2, 2012, at 11:47 AM, ext song.7@nokia.com mailto:song.7@nokia.com>> wrote: Hi, >From the Qt build system, does any file decide the QtGui depending on the >PlatformSup

[Development] QtGui depends on libPlatformSupport.a

Hi, >From the Qt build system, does any file decide the QtGui depending on the >PlatformSupport lib ? Any information is appreciated ;) Thanks, Song ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/d

Re: [Development] Color Profile support on Qt

On Aug 2, 2012, at 10:58 AM, ext Paul Olav Tvete wrote: > On Thursday 02 August 2012 10:31:59 ext Olivier Goffart wrote: >> If that's only a documentation problem, we can workaround that with some >> macro magic. > > Very good point. For some reason I thought we would have to hack on qdoc > it

Re: [Development] Color Profile support on Qt

On Thursday 02 August 2012 10:31:59 ext Olivier Goffart wrote: > If that's only a documentation problem, we can workaround that with some > macro magic. Very good point. For some reason I thought we would have to hack on qdoc itself, but creative use of \fn and \internal should be enough. > Sh

Re: [Development] state of Qt's Australia office

I'm sure QML/QtQuick will live on - only Brisbane is affected. I'm not sure if/how we, the Brisbane developers, will continue to contribute, however. Br, Martin. From: ext qtnext [qtn...@gmail.com] Sent: Thursday, 2 August 2012 4:46 PM To: Jones Martin (Nokia-M

Re: [Development] Color Profile support on Qt

On Thursday 02 August 2012 10:03:15 Paul Olav Tvete wrote: > On Thursday 02 August 2012 07:53:25 ext gunnar.sle...@nokia.com wrote: > > On Aug 1, 2012, at 6:37 PM, ext Stephen Kelly wrote: > > > Hi there, > > > > > > Given that https://codereview.qt-project.org/#change,31387 has been > > > merged,

[Development] [Qt 4.8 with directfb]Web image rendering problem

Hi all, I'm trying to view http://www.youtube.com/leanback using QTWebKit in Qt4.8.1(configure with -plugin-gfx-directfb option). There are some images in the web page seems that Qt4.8 isn't able to render them correctly. If I use Qt4.7.4 with directfb, all images are rendered correc

Re: [Development] Color Profile support on Qt

On Thursday 02 August 2012 07:53:25 ext gunnar.sle...@nokia.com wrote: > On Aug 1, 2012, at 6:37 PM, ext Stephen Kelly wrote: > > Hi there, > > > > Given that https://codereview.qt-project.org/#change,31387 has been > > merged, can you post any more information that will last until the > > QColorP