On quarta-feira, 16 de outubro de 2013 15:36:44, Olivier Goffart wrote:
> Is there really an advantage of using this, which cannot work with complex
> expression vs.
>
> #ifdef Q_OS_WIN
> Q_DECL_DEPRECATED_X("Not avaialble on windows")
> #endif
> void myFunction();
I don't want "not available"
The Q_DECL_DEPRECATED_CONDITIONAL turned out to be more limited than I was
anticipating. I think using Q_DECL_DEPRECATED_X surrounded by ifdefs would
be more explicit and accurate.
On Wed, Oct 16, 2013 at 8:36 AM, Olivier Goffart wrote:
> On Saturday 12 October 2013 18:33:00 Keith Gardner wrot
On Saturday 12 October 2013 18:33:00 Keith Gardner wrote:
> > > I had an idea about making conditional deprecation warnings for
> > > functions
> > > in Qt based on the destination platform.
> >
> > That might be useful, actually.
> >
> > But not for this case. Trying to call nativeArguments() on
> > I had an idea about making conditional deprecation warnings for functions
> > in Qt based on the destination platform.
>
> That might be useful, actually.
>
> But not for this case. Trying to call nativeArguments() on a non-Windows
> platform already signals the problem with a full error. It's
On sexta-feira, 11 de outubro de 2013 11:30:23, Keith Gardner wrote:
> I had an idea about making conditional deprecation warnings for functions
> in Qt based on the destination platform. The idea would be to get a
> compile time warning when using a function on a platform that the function
> does
I had an idea about making conditional deprecation warnings for functions
in Qt based on the destination platform. The idea would be to get a
compile time warning when using a function on a platform that the function
does not supported. An example would be calling
QProcess::nativeArguments() on n
