On 10.05.23 01:21, Thiago Macieira wrote:
> On Tuesday, 2 May 2023 17:39:01 PDT Thiago Macieira wrote:
>> Opinions?
>
> BTW, here's the opinion of the GCC devs:
>
> Don't ever use the -std= option to raise the language from the default. That
> implies opting in to functionality that they're not e
On 09.05.23 22:15, Allan Sandfeld Jensen wrote:
> On Dienstag, 9. Mai 2023 08:51:37 CEST Marc Mutz via Development wrote:
[...]
>> - space after template and before <:
>>
>> // WRONG
>> template
>> // CORRECT:
>> template
>>
>
>> Rationale: We always used the latter in Qt.
>
> We
Qt 6.5 status
* Qt 6.5.1 content is not frozen yet
* the last changes are integrating.
* Target is to freeze the release content later this week
* Target is to release Qt 6.5.1 during next week
Qt 6.6 status
* Unfortunately no new snapshot available yet.
* No suc
On Tuesday, 2 May 2023 17:39:01 PDT Thiago Macieira wrote:
> Opinions?
BTW, here's the opinion of the GCC devs:
Don't ever use the -std= option to raise the language from the default. That
implies opting in to functionality that they're not entirely satisfied with,
and may possibly still break
On Dienstag, 9. Mai 2023 08:51:37 CEST Marc Mutz via Development wrote:
> Hi,
>
> I'd like to propose the following clarifications:
>
> - no space between "operator" and it's symbol:
>
> // WRONG
> bool operator ==()
> // CORRECT
> bool operator==()
>
> Rationale: th
On Tue, May 09, 2023 at 06:51:37AM +, Marc Mutz via Development wrote:
> Hi,
>
> I'd like to propose the following clarifications:
>
> - no space between "operator" and it's symbol:
> [...]
> - exactly one space each between if and constexpr/constinit and
> [...]
> - space after template and
I made a pipeline to receive rtsp streaming with vah264dec
compliance=flexible.The pipeline runs fine from command line. But there is an
error when I use gstreamer code
to build the pipeline in C/C++. The error shows the property compliance is not
set properly.When I set int 3(flexible) to the
Hi!
+1 to all suggestions
Best regards,
Ivan
From: Development on behalf of Marc Mutz
via Development
Sent: Tuesday, May 9, 2023 8:51 AM
To: qt-dev
Subject: [Development] Proposing changes to https://wiki.qt.io/Qt_Coding_Style
Hi,
I'd like to propose the fo
> On 2 May 2023, at 11:36, Edward Welbourne wrote:
>> This email is the anchor for various topics. I’ll start with a few
>> threads with things that I remember and feel could be improved. If you
>> have something new, please start a new thread in reply to this email, ...
>
> OK, then (see Subject
On Monday, 8 May 2023 23:51:37 PDT Marc Mutz via Development wrote:
>// WRONG
>template
>// CORRECT:
>template
>
> Rationale: We always used the latter in Qt. Then a faulty _clang-format
> that dropped the space for unknown reasons was added to qt5.git and
> since then, we have a
Hi,
On behalf of the dev team working on the Qt and VS integration, I would like to
request a new repository where we can base a .NET integration module that we've
recently been working on.
Name of the repository: qt-labs/qtdotnet.git
Description: The Qt/.NET library enables the integration of
Hello!
> -Original Message-
> From: Development On Behalf Of
> Marc Mutz via Development
> Sent: tirsdag 9. mai 2023 08:52
> To: qt-dev
> Subject: [Development] Proposing changes to
> https://wiki.qt.io/Qt_Coding_Style
>
> Hi,
>
> I'd like to propose the following clarifications:
>
>
> - drop the requirement for () in lambdas
>
> Rationale: this was a word-around for older MSVCs. The standard doesn't
> require the empty parameter list (except when adorning the lambda with
> noexcept etc, and then the compiler complains) and people have voted
> with their feet: we now have many
13 matches
Mail list logo
