Re: [Development] Decrease amount of qt releases in online installer

On Wednesday, 21 February 2024 13:13:33 PST Tuukka Turunen via Development wrote: > In general we should be always guiding users towards the latest releases and > to large extent users are doing that. We should also be even faster that > currently transferring the unmaintained releases to the arch

Re: [Development] Decrease amount of qt releases in online installer

Hi, This is a good change. It has been a long time since we previously cleaned the releases available via the online installer, so the number has been growing to be quite large. In general we should be always guiding users towards the latest releases and to large extent users are doing that. W

Re: [Development] Can we remove recommendation against unnamed namespaces from Qt coding conventions?

On Wed, Feb 21, 2024 at 06:56:41PM +, Jøger Hansegård via Development wrote: > >>    Our Qt coding conventions ([1]https://wiki.qt.io/Coding_Conventions) > >>    has a statement on the use of unnamed (anonymous) namespaces. As far as > >>    I understand, this statement is now outdated. > > >

Re: [Development] Can we remove recommendation against unnamed namespaces from Qt coding conventions?

On 21.02.24 19:56, Edward Welbourne via Development wrote: Andre' Poenitz (21 February 2024 19:21) wrote: 1. 'static' is attached to individual functions, not a scope of uncertain extend. When working on unfamiliar code it helps to understand the context. With 'static' the locality is obvious i

Re: [Development] Can we remove recommendation against unnamed namespaces from Qt coding conventions?

On Wednesday, 21 February 2024 10:56:49 PST Edward Welbourne via Development wrote: > (Incidentally, the ways I can think of to say "has no name" tend to > suffer from some degree of precedent as "has a name but it has not been > disclosed" - the anonymous author of a pamphlet, the unnamed person

Re: [Development] Can we remove recommendation against unnamed namespaces from Qt coding conventions?

On Wednesday, 21 February 2024 10:56:41 PST Jøger Hansegård via Development wrote: >Use unnamed namespaces for all internal/non-exported entities. Functions > can alternatively be marked `static` in the global namespace. Marking > functions `static` also in the unnamed namespace can help reada

Re: [Development] Can we remove recommendation against unnamed namespaces from Qt coding conventions?

Andre' Poenitz (21 February 2024 19:21) wrote: > 1. 'static' is attached to individual functions, not a scope of > uncertain extend. When working on unfamiliar code it helps to > understand the context. With 'static' the locality is obvious in the > immediate context of the function and not set by

Re: [Development] Can we remove recommendation against unnamed namespaces from Qt coding conventions?

>>    Our Qt coding conventions ([1]https://wiki.qt.io/Coding_Conventions) >>    has a statement on the use of unnamed (anonymous) namespaces. As far as >>    I understand, this statement is now outdated. > [I'll assume we are talking about functions here.] Anonymous namespaces can be quite helpf

Re: [Development] Can we remove recommendation against unnamed namespaces from Qt coding conventions?

On Wed, Feb 21, 2024 at 04:26:52PM +, Jøger Hansegård via Development wrote: >Our Qt coding conventions ([1]https://wiki.qt.io/Coding_Conventions) >has a statement on the use of unnamed (anonymous) namespaces. As far as >I understand, this statement is now outdated. [I'll assume we

Re: [Development] Can we remove recommendation against unnamed namespaces from Qt coding conventions?

On Wednesday, 21 February 2024 09:19:19 PST Mathias Hasselmann via Development wrote: > How that? > > https://wiki.qt.io/Coding_Conventions#Things_to_avoid says: > > "Avoid the use of anonymous namespaces in favor of the static keyword if > possible." Back in the day, this was a better suggesti

Re: [Development] Can we remove recommendation against unnamed namespaces from Qt coding conventions?

On 21/02/2024 17:26, Jøger Hansegård via Development wrote: Our Qt coding conventions (https://wiki.qt.io/Coding_Conventions ) has a statement on the use of unnamed (anonymous) namespaces. As far as I understand, this statement is now outdated. Can we dele

Re: [Development] Can we remove recommendation against unnamed namespaces from Qt coding conventions?

Am 21.02.2024 um 17:36 schrieb Thiago Macieira: On Wednesday, 21 February 2024 08:26:52 PST Jøger Hansegård via Development wrote: Our Qt coding conventions (https://wiki.qt.io/Coding_Conventions) has a statement on the use of unnamed (anonymous) namespaces. As far as I understand, this stateme

Re: [Development] Can we remove recommendation against unnamed namespaces from Qt coding conventions?

> Our Qt coding conventions (https://wiki.qt.io/Coding_Conventions) has a > statement on the use of unnamed (anonymous) namespaces. As far as I > understand, this statement is now outdated. Can we delete this statement > and lean on Cpp Core Guidelines Cpp Core Guidelines SF.22 instead? > Or do we

Re: [Development] Can we remove recommendation against unnamed namespaces from Qt coding conventions?

On Wednesday, 21 February 2024 08:26:52 PST Jøger Hansegård via Development wrote: > Our Qt coding conventions (https://wiki.qt.io/Coding_Conventions) has a > statement on the use of unnamed (anonymous) namespaces. As far as I > understand, this statement is now outdated. Can we delete this statem

[Development] Can we remove recommendation against unnamed namespaces from Qt coding conventions?

Our Qt coding conventions (https://wiki.qt.io/Coding_Conventions) has a statement on the use of unnamed (anonymous) namespaces. As far as I understand, this statement is now outdated. Can we delete this statement and lean on Cpp Core Guidelines Cpp Core Guidelines SF.22 instead https://isocpp.g

Re: [Development] Decrease amount of qt releases in online installer

> -Original Message- > From: Development On Behalf Of > Giuseppe D'Angelo via Development > Sent: keskiviikko 21. helmikuuta 2024 13.21 > To: development@qt-project.org > Subject: Re: [Development] Decrease amount of qt releases in online installer > > Hello, > > On 21/02/2024 11:42, Jan

Re: [Development] Decrease amount of qt releases in online installer

Hello, On 21/02/2024 11:42, Jani Heikkinen via Development wrote: Currently, more than 60 Qt releases can be installed from the Qt open source online installer (if all installation categories are selected). This requires a huge amount of disk space on the mirrors and also causes some performan

[Development] Decrease amount of qt releases in online installer

Hi, Currently, more than 60 Qt releases can be installed from the Qt open source online installer (if all installation categories are selected). This requires a huge amount of disk space on the mirrors and also causes some performance issues with the online installer. That's why I suggest remov

Re: [Development] CI is currently down! Hardware issues.

Hi again. The backend seems to be working after a standard fix method was applied: power off - power on. All systems are back to normal. -Tony -- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development