> 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
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.09.2017 18:21, Thiago Macieira wrote:
On Friday, 15 September 2017 00:31:36 PDT Sami Nurmenniemi wrote:
I think we'll just have to accept blocking for the devices without
hwrng. I don't know if we really support any such devices. If we do and
boot time is essential for those, we'll have to
> 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
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 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,
> 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 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 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
> 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.
I agree regarding consistency. If we are spending time on this, then it should
be done properly. I think Qt Coding Conventions wiki should be moved to
somewhere where c
> -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 Coding style and C++11
>
> > I'd
On Monday, 18 September 2017 00:34:03 PDT Sami Nurmenniemi wrote:
> > And that would be a non-Qt job. I wasn't worried about Qt on real devices
> > because I don't expect it to be run early enough to matter. On VMs,
> > that's
> > another story, and if you don't trust your undercloud-provided /dev
Hello,
I'd like to announce the release of Qbs 1.9, which introduces major new
features product multiplexing and dependency parameterization. You can
find all the relevant information here:
https://blog.qt.io/blog/2017/09/05/qbs-1-9-released/
Cheers,
Joerg
_
Hello everyone,
I'm happy to announce that we've just added a new mirror for download.qt.io in
the San Francisco Bay Area (the first in the US west coast geographic area).
This mirror is provided by UC Berkeley and is very high-bandwidth, which should
result in a significant download performanc
14 matches
Mail list logo