On 6/30/15 1:01 PM, Thiago Macieira wrote:
On Tuesday 30 June 2015 09:37:59 Ansel Sermersheim wrote:
Our goal with CopperSpice is to use modern C++ internally to leverage
everything we can from the language. We want developers of CopperSpice
applications to have the full power of C++ available
On Wednesday 01 July 2015 00:49:19 Olivier Goffart wrote:
On Tuesday 30. June 2015 22:37:24 Bernhard wrote:
For example, with moc removed we support template classes that inherit
from QObject.
Wow. I would (almost) kill for having that feature in Qt!
You can do that with moc.
On Tuesday 30 June 2015 19:40:55 Ansel Sermersheim wrote:
Unless you're going to rewrite the entire GUI, widgets, networking and
other libraries from scratch, you're not going to get exception-safety.
Yes, many parts will need to be redone and we are starting with the
container classes.
On Friday 26. June 2015 08:41:11 Thiago Macieira wrote:
On Friday 26 June 2015 11:59:11 Olivier Goffart wrote:
However, it is questionable if even this works. We already rely on the
standard library ABI in QException. And most users will have to recompile
everything if they want to change
On 6/29/15 11:37 PM, Alejandro Exojo wrote:
El Tuesday 30 June 2015, Ansel Sermersheim escribió:
Our September release of CopperSpice will include changes to the
contain library, reimplementation of atomic types, our new changes
to the MetaObject System registration, full API documentation,
For example, with moc removed we support template classes that inherit
from QObject.
Wow. I would (almost) kill for having that feature in Qt!
--
Regards
Bernhard Lindner
___
Development mailing list
Development@qt-project.org
On Tuesday 30 June 2015 22:57:32 Jason H wrote:
I was perusing the archive of this list so I would know what to expect
tomorrow and saw that there was a suggestion to drop non C++11 compilers.
Hello Jason
Your discussion is better held in the developer mailing list. I'm Cc'ing it.
Please drop
On Tuesday 30 June 2015 09:37:59 Ansel Sermersheim wrote:
Our goal with CopperSpice is to use modern C++ internally to leverage
everything we can from the language. We want developers of CopperSpice
applications to have the full power of C++ available in all parts of
their code. For example,
On Tuesday 30 June 2015 18:16:34 Olivier Goffart wrote:
On Friday 26. June 2015 08:41:11 Thiago Macieira wrote:
On Friday 26 June 2015 11:59:11 Olivier Goffart wrote:
However, it is questionable if even this works. We already rely on the
standard library ABI in QException. And most users
On Tue, Jun 30, 2015 at 10:01 PM, Thiago Macieira thiago.macie...@intel.com
wrote:
You're making trade-offs. One of them, given your presentation, is that
there's
no current version of MSVC that will work with your codebase. Another is
that
you're replacing a code generator by a lot of
On 6/29/15 10:59 PM, Thiago Macieira wrote:
On Monday 29 June 2015 22:51:25 Ansel Sermersheim wrote:
I would like to clarify, we did not use anything from the Woboq
blog posting as others have speculated. We had moc removed from
CopperSpice a year earlier than the release of this blog. We are
On Monday 29 June 2015 22:51:25 Ansel Sermersheim wrote:
I would like to clarify, we did not use anything from the Woboq blog
posting as others have speculated. We had moc removed from CopperSpice
a year earlier than the release of this blog. We are also not
associated with the Trinity
El Tuesday 30 June 2015, Ansel Sermersheim escribió:
Our September release of CopperSpice will include changes to the
contain library, reimplementation of atomic types, our new changes to
the MetaObject System registration, full API documentation, ??
We would like to encourage developers to
On Tuesday 30 June 2015 23:09:59 Cristian Adam wrote:
On Tue, Jun 30, 2015 at 10:01 PM, Thiago Macieira thiago.macie...@intel.com
wrote:
You're making trade-offs. One of them, given your presentation, is that
there's
no current version of MSVC that will work with your codebase.
On Tuesday 30. June 2015 22:37:24 Bernhard wrote:
For example, with moc removed we support template classes that inherit
from QObject.
Wow. I would (almost) kill for having that feature in Qt!
You can do that with moc.
https://codereview.qt-project.org/49864/
There was a discussion about
15 matches
Mail list logo
