Hi Kevin,
Am 15.11.2017 um 17:39 schrieb Kevin Funk:
On Monday, 18 September 2017 10:03:40 CET Kevin Funk wrote:
On Monday, 18 September 2017 09:38:53 CEST Ville Voutilainen wrote:
On 18 September 2017 at 10:36, Lars Knoll wrote:
But for new plugins that target a known platform that supports
On Monday, 18 September 2017 10:03:40 CET Kevin Funk wrote:
> On Monday, 18 September 2017 09:38:53 CEST Ville Voutilainen wrote:
> > On 18 September 2017 at 10:36, Lars Knoll wrote:
> > >>> But for new plugins that target a known platform that supports c++11,
> > >>> they can most likely use new
On Friday, 15 September 2017 10:47:02 CEST Kevin Funk wrote:
> On Friday, 15 September 2017 06:42:34 CEST André Hartmann wrote:
> > Hi, since a while C++11 is allowed in Qt and there is ongoing effort
> > porting e.g. examples to the new possibilities.
>
> Slightly OT but I hope still useful: I'm
> -Original Message-
> From: Development [mailto:development-bounces+kai.koehne=qt.io@qt-
> project.org] On Behalf Of Gatis Paeglis
> Sent: Monday, September 18, 2017 12:43 PM
> To: André Hartmann ; development@qt-project.org
> Subject: Re: [Development] Qt Codi
50/3/examples/widgets/itemviews/storageview/storagemodel.h
Gatis.
From: Development on
behalf of André Hartmann
Sent: Friday, September 15, 2017 6:42:34 AM
To: development@qt-project.org
Subject: [Development] Qt Coding style and C++11
Hi, since a while C++11 is al
On 09/15/2017 06:42 AM, André Hartmann wrote:
I'd like to push this discussion, because if code is converted to a
new base, it should be clear to everyone HOW to do so.
Great initiative! It would be great if the guidelines could be updated
to reflect the new standard.
What I like to add, is to e
On Monday, 18 September 2017 09:38:53 CEST Ville Voutilainen wrote:
> On 18 September 2017 at 10:36, Lars Knoll wrote:
> >>> But for new plugins that target a known platform that supports c++11,
> >>> they can most likely use new conventions. Unless someone can come up
> >>> with technical reasons
> On 18 Sep 2017, at 09:37, André Somers wrote:
>
> Op 18/09/2017 om 09:02 schreef Lorn Potter:
>>> On 15 Sep 2017, at 6:47 pm, Kevin Funk wrote:
>>>
>>> (2) And maybe your request:
>>> - Use C++11 member initialization where possible
>>> (IOW: Run clang-tidy cppcoreguidelines-pro-type-member-
On 18 September 2017 at 10:36, Lars Knoll wrote:
>>> But for new plugins that target a known platform that supports c++11, they
>>> can most likely use new conventions.
>>> Unless someone can come up with technical reasons the new c++11 member
>>> initialization is better than what is there now,
Op 18/09/2017 om 09:02 schreef Lorn Potter:
>> On 15 Sep 2017, at 6:47 pm, Kevin Funk wrote:
>>
>> (2) And maybe your request:
>> - Use C++11 member initialization where possible
>> (IOW: Run clang-tidy cppcoreguidelines-pro-type-member-init checker
>> on code base and apply all fixes)
> But t
> On 18 Sep 2017, at 09:25, Ville Voutilainen
> wrote:
>
> On 18 September 2017 at 10:02, Lorn Potter wrote:
The section "Conventions for C++11 usage" in [1] states:
"Note: This section is not an accepted convention yet.
This section serves as baseline for further discuss
On 18 September 2017 at 10:02, Lorn Potter wrote:
>>> The section "Conventions for C++11 usage" in [1] states:
>>>
>>> "Note: This section is not an accepted convention yet.
>>> This section serves as baseline for further discussions."
>>>
>>> I'd like to push this discussion, because if code i
> On 15 Sep 2017, at 6:47 pm, Kevin Funk wrote:
>
> (2) And maybe your request:
> - Use C++11 member initialization where possible
> (IOW: Run clang-tidy cppcoreguidelines-pro-type-member-init checker
> on code base and apply all fixes)
But then files will begin to have a mixture of the two c
Hi Kevin,
Am 15.09.2017 um 10:47 schrieb Kevin Funk:
On Friday, 15 September 2017 06:42:34 CEST André Hartmann wrote:
Hi, since a while C++11 is allowed in Qt and there is ongoing effort
porting e.g. examples to the new possibilities.
Slightly OT but I hope still useful: I'm out of the loop h
On Friday, 15 September 2017 06:42:34 CEST André Hartmann wrote:
> Hi, since a while C++11 is allowed in Qt and there is ongoing effort
> porting e.g. examples to the new possibilities.
Slightly OT but I hope still useful: I'm out of the loop how you are doing
these code transformations, but refa
Hi, since a while C++11 is allowed in Qt and there is ongoing effort
porting e.g. examples to the new possibilities.
The section "Conventions for C++11 usage" in [1] states:
"Note: This section is not an accepted convention yet.
This section serves as baseline for further discussions."
I'd
16 matches
Mail list logo
