Thank you for visiting the BlackBerry Support Community Forums.
BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)
BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.
"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."
- Kevin Michaluk, Founder, CrackBerry.com
Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.
03-18-2013 12:33 PM
The solution would be lots of noisy developers to display interested in immediate C++ 11 support. Then Blackberry might decide to be nice and to enable proper support. I am serious!
One of the lead platform developers wrote a month or so ago that currently qcc doesn't support C++11 or something like that. Go and vote/file a request for C++11 support.
03-18-2013 12:42 PM
It's possible to use some of it (lambdas, auto, raw strings), although I don't know how safe. Seems okay for me. Use at your own risk:
Under compiler options, add: -std=c++0x
Under Preprocessor Options, use: -U__GXX_EXPERIMENTAL_CXX0X__
This is so that any external headers you include don't use glib's special constructors for the stl.
I then made my own unique_ptr and move, forward.
I think the main problem with the c++0x and QNX is that QNX uses it's own STL (possibibly a modified Dinkum).
03-18-2013 12:55 PM
I don't know about Qt5 but as I've written above one of the developers commented that it is disabled for the NDK. You can find that in bugreports.qt-project.org if you are interested. Do you use Linux or Windows?
BTW What is the status of Qt 5 currently? Is it OK to start a graphics intensive project (with or without using C++11) and hope to finish/publish it in few months?
03-18-2013 12:58 PM
03-18-2013 01:08 PM - edited 03-18-2013 02:55 PM
And you are developing on Linux? (this is the link to the issue I've written above - the last post https://bugreports.qt-project.org/browse/QTBUG-289