On quarta-feira, 2 de outubro de 2013 05:42:24, Knoll Lars wrote:
> On 01.10.13 23:23, "Thiago Macieira" <thiago.macie...@intel.com> wrote:
> >On terça-feira, 1 de outubro de 2013 20:00:56, Knoll Lars wrote:
> >> Yes, signal/slot connections between user code should IMO still be able
> >>to
> >> pass through exceptions. I am afraid removing that will break code
> >>that's
> >> out there.
> >
> >This is already forbidden since 5.0.
> 
> Is there any good reason why we don't support this, as we did in Qt 4? My
> goal of still compiling Qt Core with exceptions enabled was to allow for
> exactly this use case.

Because we don't test it, so there's no guarantee that it works. In fact, I'd 
be surprised if it works at all. What's more, our types aren't exception-safe, 
even the container types. It's entirely unknown what will happen during a 
stack unwind.

Personally, I don't want to maintain that functionality.

And then there's the question: is it worth the 7% increase in code size?

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Reply via email to