Spam detection software, running on the system "mx.qt-project.org",
has identified this incoming email as possible spam. The original
message has been attached to this so you can view it or label
similar future email. If you have any questions, see
the administrator of that system for details.
Content preview: On 9/6/19 4:27 PM, Mutz, Marc via Development wrote: > Yes,
and no. No, the enums are still defined in namespace Qt. Yes, the > Qt::
prefix is then optional, so a user name AlignLeft would conflict at > the
source level, giving a ambiguity error, fixable by explicit > prefixing with
Qt:: [...]
Content analysis details: (4.1 points, 4.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60%
[score: 0.4985]
0.0 SPF_HELO_NONE SPF: HELO does not publish an SPF Record
1.0 RDNS_DYNAMIC Delivered to internal network by host with
dynamic-looking rDNS
0.0 KHOP_HELO_FCRDNS Relay HELO differs from its IP's reverse DNS
2.3 FORGED_MUA_MOZILLA Forged mail pretending to be from Mozilla
--- Begin Message ---
On 9/6/19 4:27 PM, Mutz, Marc via Development wrote:
Yes, and no. No, the enums are still defined in namespace Qt. Yes, the
Qt:: prefix is then optional, so a user name AlignLeft would conflict at
the source level, giving a ambiguity error, fixable by explicit
prefixing with Qt::
But how to fix the ambiguity if you want the "user name AlignLeft" - by
writing ::AlignLeft ?
And what if AlignLeft is defined in some third party library header. The
author of that library might not even know about Qt, but the application
that uses that library together with Qt will run into compiler problems.
My 2 cents,
Uwe
--- End Message ---
_______________________________________________
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
