On Saturday, 8 May 2021 23:55:36 PDT Alberto Mardegan wrote:
> yes, I knew that long changes size depending on the architecture, but:
> > As far as I am concerned, the fact that
> > int64_t, size_t and ptrdiff_t sometimes (not always!) use long is a
> > misfeature. Those decisions were made in the
Hi Tiago,
On 08/05/21 18:47, Thiago Macieira wrote:
> And the problem is that they *do* depend on the CPU architecture. long
> changes
> size depending on OS and pointer size.
yes, I knew that long changes size depending on the architecture, but:
> As far as I am concerned, the fact that
> in
On Saturday, 8 May 2021 00:48:51 PDT Alberto Mardegan wrote:
> Hi there!
> I'm struggling to understand what's going on with types being
> marshalled onto D-Bus, and I'd like to understand if what I'm seeing is
> a but with the Qt version I'm using (Qt 5.12.7 + some patches), an issue
> with the
On 08/05/21 10:48, Alberto Mardegan wrote:
> Interestingly, I'm seeing this on amd64 only; it seems that on armhf
> everything is working fine. Could it be a bug with the compiler?
In armhf, QMetaType::type("int64_t") always returns 4 (LongLong), even
before registering the metatype (maybe this st
Hi there!
I'm struggling to understand what's going on with types being
marshalled onto D-Bus, and I'd like to understand if what I'm seeing is
a but with the Qt version I'm using (Qt 5.12.7 + some patches), an issue
with the compiler, or just the expected behaviour.
The problem is that QtDBus f
