On Tue, 10 Nov 2020 at 07:47, Giuseppe D'Angelo via Development <
development@qt-project.org> wrote:
> To avoid repeating myself a bit too often in code reviews, I've put
> together some notes in a QUIP (18), available here
>
Hi Giuseppe,
It seems that there is a clash in the quip numbers. Ther
Hi Everyone,
We have released Qt 5.12.10 today, see
https://www.qt.io/blog/qt-5.12.10-released
Thanks to everyone involved!
br,
Jani Heikkinen
Release Manager
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinf
Hi,
To avoid repeating myself a bit too often in code reviews, I've put
together some notes in a QUIP (18), available here
https://codereview.qt-project.org/c/meta/quips/+/321050
The latest pre-rendered draft is also attached. For once, I'd like to
kickstart a discussion here rather than on
Hi again!
On Mon, 9 Nov 2020 at 15:51, Shawn Rutledge wrote:
>
>
>
> > On 9 Nov 2020, at 19:27, Shawn Rutledge wrote:
> >
> >
> >> On 2 Nov 2020, at 17:15, Thiago Macieira wrote:
> >> ]qml is like Python: because of plugins, it's tied to the Qt version.
> >> Therefore, it fails the requirement
> On 9 Nov 2020, at 19:27, Shawn Rutledge wrote:
>
>
>> On 2 Nov 2020, at 17:15, Thiago Macieira wrote:
>> ]qml is like Python: because of plugins, it's tied to the Qt version.
>> Therefore, it fails the requirement for supporting everything the old
>> version
>> supported.
>
> Well if y
Hi!
On Mon, 9 Nov 2020 at 15:28, Shawn Rutledge wrote:
>
>
> > On 2 Nov 2020, at 17:15, Thiago Macieira wrote:
> > ]qml is like Python: because of plugins, it's tied to the Qt version.
> > Therefore, it fails the requirement for supporting everything the old
> > version
> > supported.
>
> Well
> On 2 Nov 2020, at 17:15, Thiago Macieira wrote:
> ]qml is like Python: because of plugins, it's tied to the Qt version.
> Therefore, it fails the requirement for supporting everything the old version
> supported.
Well if you were using modules that are no longer supported, or you run into
Hi!
On Mon, 2 Nov 2020 at 13:17, Thiago Macieira wrote:
>
> On Monday, 2 November 2020 06:21:49 PST Shawn Rutledge wrote:
> > Sorry for snipping so much, but it seems like all your arguments are about
> > tools that are used to build software (qmake, moc etc.). And you have a
> > point there.
>
Hi!
On Mon, 2 Nov 2020 at 10:09, Lars Knoll wrote:
>
> I honestly don't think renaming all our binaries is an option, certainly not
> that late in the process. We’ve had Qt 4 and Qt 5 co-installed for a long
> time as well and while that might not be perfect it was working.
>
> And qtchooser ha
Hello,
On 09/11/2020 11:33, Lars Knoll wrote:
Q_PRIMITIVE_TYPE specifies that Type is a POD (plain old data) type with no
constructor or destructor, or else a type where every bit pattern is a valid
object and memcpy() creates a valid independent copy of the object.
With this definition in mi
> On 9 Nov 2020, at 10:25, Giuseppe D'Angelo via Development
> wrote:
>
> Hi,
>
> I have been wondering whether Q_PRIMITIVE_TYPE could be phased out and its
> support removed (kept for SC, but effectively it simply becomes synonymous
> for Q_MOVABLE_TYPE).
>
> First and foremost, there see
Hi,
I have been wondering whether Q_PRIMITIVE_TYPE could be phased out and
its support removed (kept for SC, but effectively it simply becomes
synonymous for Q_MOVABLE_TYPE).
First and foremost, there seems to be disagreement on what "primitive
type" means. From the docs:
Q_PRIMITIVE_TYPE
12 matches
Mail list logo
