On 25/02/16 18:02, "Development on behalf of Thiago Macieira"
wrote:
>On quinta-feira, 25 de fevereiro de 2016 17:33:52 PST Cristian Adam wrote:
>> This might be a burden for some of the Qt developers (Windows ones).
>>
>> But all the Qt users get a modern / flexible moc, see this thread:
>>
On sábado, 27 de fevereiro de 2016 11:54:35 PST Olivier Goffart wrote:
> > It's probably the same discussion as the almost-always-auto we had before,
> > but since we're talking about the public interface of something, I'd
> > expect
> > people to write their types more often than just relying on t
Am Freitag, 26. Februar 2016, 09:02:27 CET schrieb Thiago Macieira:
> On quinta-feira, 25 de fevereiro de 2016 18:36:16 PST Olivier Goffart wrote:
> > The parser need to be adapted if we want to support trailing type for
> > signals/ slots/Q_INVOKABLE; or C++11 attributes; decltype as argument type
On quinta-feira, 25 de fevereiro de 2016 18:36:16 PST Olivier Goffart wrote:
> The parser need to be adapted if we want to support trailing type for
> signals/ slots/Q_INVOKABLE; or C++11 attributes; decltype as argument type
> for invokable; or fancy default arguments. There might be other things.
Am Donnerstag, 25. Februar 2016, 09:02:11 CET schrieb Thiago Macieira:
> On quinta-feira, 25 de fevereiro de 2016 17:33:52 PST Cristian Adam wrote:
> > This might be a burden for some of the Qt developers (Windows ones).
> >
> > But all the Qt users get a modern / flexible moc, see this thread:
>
On quinta-feira, 25 de fevereiro de 2016 17:33:52 PST Cristian Adam wrote:
> This might be a burden for some of the Qt developers (Windows ones).
>
> But all the Qt users get a modern / flexible moc, see this thread:
> https://www.reddit.com/r/cpp/comments/470ama/qt_moc_myths_debunked/d09c90e
I d
On Thu, Feb 25, 2016 at 5:15 PM, Thiago Macieira
wrote:
> On quinta-feira, 25 de fevereiro de 2016 11:20:16 PST Cristian Adam wrote:
> > Since qdoc will be using libclang, any change of getting the same
> treatment
> > for moc?
>
> I don't think that's a good idea. We can't require people to inst
On quinta-feira, 25 de fevereiro de 2016 11:20:16 PST Cristian Adam wrote:
> Since qdoc will be using libclang, any change of getting the same treatment
> for moc?
I don't think that's a good idea. We can't require people to install Perl in
order to compile Qt. Requiring them to install and build
On Thursday 25 February 2016 10:56:01 Smith Martin wrote:
> Send ideas for upgrading the Qt documentation to C++11.
>
>
> 1. Which C++11 constructs will be used in Qt?
>
>
> 2. Which of these should appear in the documentation?
>
>
> Send comments to the CC list.
It would be nice if std:: ty
Hi,
From: Smith Martin [mailto:martin.sm...@theqtcompany.com]
Sent: Donnerstag, 25. Februar 2016 12:17 Uhr
To: Heimrich Karsten ;
development@qt-project.org
Subject: Re: [Development] We are planning to upgrade qdoc to use clang for
parsing C++
I'm stating it now. What is your obje
I'm stating it now. What is your objection?
martin
From: Development
on behalf of
Karsten Heimrich
Sent: Thursday, February 25, 2016 12:08 PM
To: development@qt-project.org
Subject: Re: [Development] We are planning to upgrade qdoc to use clang for
pa
Hi,
From: Development
[mailto:development-bounces+karsten.heimrich=theqtcompany@qt-project.org]
On Behalf Of Cristian Adam
Sent: Donnerstag, 25. Februar 2016 11:20 Uhr
To: Smith Martin
Cc: development@qt-project.org
Subject: Re: [Development] We are planning to upgrade qdoc to use clang
From: Nowacki Jedrzej
Sent: Thursday, February 25, 2016 11:10 AM
To: development@qt-project.org
Cc: Smith Martin
Subject: Re: [Development] We are planning to upgrade qdoc to use clang for
parsing C++
On Thursday 25 of February 2016 09:56:01 Smith Martin wrote:
> Send ideas for up
On Thu, Feb 25, 2016 at 10:56 AM, Smith Martin <
martin.sm...@theqtcompany.com> wrote:
> Send ideas for upgrading the Qt documentation to C++11.
>
>
> 1. Which C++11 constructs will be used in Qt?
>
>
> 2. Which of these should appear in the documentation?
>
>
> Send comments to the CC list.
>
Si
On Thursday 25 of February 2016 09:56:01 Smith Martin wrote:
> Send ideas for upgrading the Qt documentation to C++11.
>
> 1. Which C++11 constructs will be used in Qt?
All of them, in longer run C++14 too :-)
> 2. Which of these should appear in the documentation?
I do not understand the question
Send ideas for upgrading the Qt documentation to C++11.
1. Which C++11 constructs will be used in Qt?
2. Which of these should appear in the documentation?
Send comments to the CC list.
martin
___
Development mailing list
Development@qt-project.
16 matches
Mail list logo
