[Interest] QT_NO_EXCEPTIONS

[Thiago Macieira]

On segunda-feira, 20 de janeiro de 2014 12:21:14, Alex Merry wrote:
> This means that QT_NO_EXCEPTIONS matches whether the user of Qt is being
> compiled with exceptions, rather than Qt itself, and so the headers may
> not always match the library code.  

That's because no matching is required. It's used only to decide if inline 
code should try to use try / catch or instead do something different.

> An obvious example is that you may
> end up with QException declared but not defined, and various
> header-defined methods of, say, QFutures look like they could call the
> potentially-undefined QFutureInterfaceBase::reportException.

No issue, since QtConcurrent is always compiled with exceptions enabled.

> So my question: is this sane/intended behaviour?  Or am I missing something?

Yes, it's intended. You're missing that the code that works with exceptions is 
always compiled with exceptions enabled.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20140120/96f515b1/attachment.sig>