I don't want to take the Qt containers away from Qt users. I want to get
rid of their use in our APIs, so that both the Qt implementation as well
as our users are free to choose the best container for their needs
instead of having to pick from one of the public Qt containers.
I would like to kno
Qt 6.4 status:
- Branching from '6.4' to '6.4.1' done
- Final fixes for Qt 6.4.1 integrating
- Target is to freeze the Qt 6.4.1 content Wed 9th November
- Target is to release Qt 6.4.1 Tue 15th November
Qt 6.5 status:
- Public snapshot from 'dev' available and updated automatically
- Preparations
Hi Andre,
When you say
> You, /personally/ /you/, have been the driving force
I think you and Kevin are giving me credit where none is due. The Qt
containers changed multiple times before the Qt project was even formed
and yours truly could have possibly had any influence on their design.
In
On Tuesday, 8 November 2022 12:59:39 PST Niclas Rosenvik wrote:
> /home/qt/work/qt/qtbase/build/target/include/QtCore/../../../../src/corelib/
> ipc/qtipccommon.h:125:21: warning: 'QNativeIpcKey::TypeAndFlags::type' is
> too small to hold all values of 'enum class QNativeIpcKey::Type'
This one is
On Tue, 08 Nov 2022 10:35:08 -0800
Thiago Macieira wrote:
> On Saturday, 5 November 2022 22:59:06 PST Thiago Macieira wrote:
> > Ok, now I need QNX help from build
> > https://testresults.qt.io/coin/integration/qt/qtbase/tasks/1679395790
>
> ping, anyone?
>
> I've updated the configure summary
On Mon, Nov 07, 2022 at 08:15:58PM +, Marc Mutz via Development wrote:
> Hi all,
>
> SCNR taking the proffered bait:
>
> On 07.11.22 18:51, Edward Welbourne wrote:
> > For Qt to remain relevant in the rapidly-evolving C++ landscape, it
> > needs to change; but one of its strong selling-points
On Saturday, 5 November 2022 22:59:06 PST Thiago Macieira wrote:
> Ok, now I need QNX help from build
> https://testresults.qt.io/coin/integration/qt/qtbase/tasks/1679395790
ping, anyone?
I've updated the configure summary to include whether the key was enabled and
it was indeed NOT enabled:
-
Hi,
This information was already published on this list, but it seems to have been
missed by a handful of key players (possibly because it was only included in
the Maintenance break email). Risking informing you all twice, I’ll reiterate
the memo here.
—
IMPORTANT: Server host keys have been
> On 8 Nov 2022, at 14:25, Volker Hilsheimer via Development
> wrote:
👏🏻
Tor Arne
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
> On 7 Nov 2022, at 21:15, Marc Mutz via Development
> wrote:
[…]
> Anyway; to all those who disagree when I say Qt should concentrate on
> its core competencies and stop meddling with container classes, shared
> pointers, etc, I say this: which of the two universes above would you
> rather
--
Alex
> -Original Message-
> From: Development On Behalf Of
> Volker Hilsheimer via Development
> Sent: Monday, 7 November 2022 16:51
> To: Marc Mutz ; development@qt-project.org
> Subject: Re: [Development] How qAsConst and qExchange lead to qNN
>
> > On 4 Nov 2022, at 16:00, Marc M
11 matches
Mail list logo
