On 2018-10-31 16:46, Thiago Macieira wrote:
Qt6 won't be fully source-compatible. The idea is that we'll break it
to fix
things, but attempt to keep compatible as much as possible to avoid
death by a
thousand paper cuts.
Does this rule out some kind of smart pointer that would be used to
On Monday, February 25, 2013 05:12:48 PM Joerg Bornemann wrote:
On 25/02/2013 16:27, Jake Thomas Petroules wrote:
I'd prefer Qt namespace with no platform indicators, i.e.:
Qt::toHICON
Qt::toHBITMAP
Qt::toCGImageRef
Qt::toNSString
It's obvious to which platform each function
On Monday, February 25, 2013 05:50:06 PM Joerg Bornemann wrote:
On 25/02/2013 17:25, Sascha Cunz wrote:
Why would a function that is potentially useful on more than one
platform go to platform extras?
Because it's working on native types (more than just one) and encoding
all type names
On Monday, February 18, 2013 07:18:44 AM Stephen Kelly wrote:
On Monday, February 18, 2013 03:27:32 Sascha Cunz wrote:
I am using FIND_PACKAGE and QT_USE_MODULES in each subdirectory of
my cmake source tree like shown in [2]. This is required, because I have a
generic stub that encapsules
Hi Stephen,
after the merge from [stable] to [dev] branch, my jenkins server noticed that
there is a problem with compiling my stacks against Qt5.
After looking over all the changes, I found out that there is an issue with the
gerrit change 47230 [1] and am trying to find a way to solve or at
Am Freitag, 11. Januar 2013, 23:07:25 schrieb Shaw Andy:
[...]
Microsoft in the past has also said that you should keep the
-MD(d)/-MT(d)
setting consistent so it is the same across all libraries and
applications,
[...]
Which is cool, if you can manage it. But it's far
[...]
The difference is that 'operate' and 'configure' are two different tasks
and thus usually require two different interfaces.
The 'operate' interface of an anti-malware service is to monitor data
and network traffic. The 'configure' interface is most probably a
seperate application
All services/daemons must be able to interface with other processes:
Here, I almost agree :-)
(a)- a client-process can request-a-client-operation to occur on that
service/daemon
But this is totally orthogonal to the application being a daemon/service. To
some daemons your application
Am Dienstag, 27. November 2012, 08:16:20 schrieb Lukas Geyer:
Am 27.11.2012 06:15, schrieb Sascha Cunz:
A daemon/service has two interfaces: (i) user/system-API oriented, and
(ii)
one internal.
The first presents the interface to the outside world on how to control
the
service
