At 2013/6/14 23:18, Friedemann Kleint wrote:
Hi,
For your information, we are planning to re-add tablet support (larval
stage at https://codereview.qt-project.org/#change,58971 ).
Friedemann
--
Friedemann Kleint
Digia, Qt
___
Development mailing
On sexta-feira, 14 de junho de 2013 16.25.28, Thiago Macieira wrote:
> On sábado, 15 de junho de 2013 00.59.18, Giuseppe D'Angelo wrote:
> > On 15 June 2013 00:37, Thiago Macieira wrote:
> > > C++11 did not change the meaning of the keyword. This is a completely
> > > made-up warning by Clang, lik
On sábado, 15 de junho de 2013 00.59.18, Giuseppe D'Angelo wrote:
> On 15 June 2013 00:37, Thiago Macieira wrote:
> > C++11 did not change the meaning of the keyword. This is a completely
> > made-up warning by Clang, like the GCC warning that says const in prvalue
> > return types makes no sense
On sexta-feira, 14 de junho de 2013 23.24.50, Giuseppe D'Angelo wrote:
> On 14 June 2013 11:44, Stephen Kelly wrote:
> > http://thread.gmane.org/gmane.comp.compilers.clang.scm/74932
> >
> > This will be quite noisy for Qt and for users of Qt. Should we remove the
> > use of register from Qt? Or
The only macro that could make sense seems to be
#define register
I say +1 for removal since 'register' is just noise, and if any compiler
actually still uses this flag it will typically just cause less optimized
code.
On Fri, Jun 14, 2013 at 4:48 PM, Thiago Macieira
wrote:
> On sexta-feira, 14
Hi,
For your information, we are planning to re-add tablet support (larval
stage at https://codereview.qt-project.org/#change,58971 ).
Friedemann
--
Friedemann Kleint
Digia, Qt
___
Development mailing list
Development@qt-project.org
http://lists.qt
On sexta-feira, 14 de junho de 2013 11.44.00, Stephen Kelly wrote:
> This will be quite noisy for Qt and for users of Qt. Should we remove the
> use of register from Qt? Or replace it with Q_REGISTER which is empty for
> c++11?
Either remove or disable the warning. A macro makes no sense for this
Hi,
Message: 1
> Date: Sat, 8 Jun 2013 16:28:45 +
> From: Salovaara Akseli
> Subject: [Development] Qt 4.8.5 Release Candidate 2 available & new
> sha1
> To: "development@qt-project.org"
> Message-ID:
> <8ee30b3f13f8c042bffad90938b94a6f4d8fb...@it-exmb02-hki.it.local>
> Cont
On Friday, June 14, 2013 11:52:37 Heikkinen Jani wrote:
> Hi all!
>
> Last night we succeed to create new packages with updated content(based on
> qt5.git from yesterday) and now we are really close to Qt5.1 RC1. According
> to our understanding these two changes are still needed before we can
> c
Hi all!
Last night we succeed to create new packages with updated content(based on
qt5.git from yesterday) and now we are really close to Qt5.1 RC1. According to
our understanding these two changes are still needed before we can create final
RC1 packages but does anyone know something else whic
Most of you don't know that qdoc can/used to generate the Qt documentation in
DITA XML format. At that time (Nokia era), we envisioned generating all the
documentation in DITA XML (not just Qt), storing it in a database, and
publishing subsets of it as needed using available tools.
That was th
Hi,
A recent patch to clang enables a warning for any use of the register storage
class specifier when -std=c++11 is used.
$ ~/dev/build/qtbase/llvm/bin/clang++ -std=c++11 -fPIE -
I$HOME/dev/prefix/qtbase/include -c
~/dev/src/qtbase/src/corelib/tools/qstring.h
clang-3.4: warning: treating
12 matches
Mail list logo