On Wednesday, May 09, 2012 11:30:35 AM lars.kn...@nokia.com wrote: > On 5/9/12 12:33 PM, "ext Olivier Goffart" <oliv...@woboq.com> wrote: > >On Wednesday 09 May 2012 11:28:30 Giuseppe D'Angelo wrote: > >> On 9 May 2012 10:22, Olivier Goffart <oliv...@woboq.com> wrote:
[snip] > Actually I wonder why we don't compile all of Qt with exceptions disabled > by default and enable them only for the places they are really needed > (QtCore for exception safe signal/slot connections etc, and QtXmlPatterns > because it uses them). Can anybody come up with a good reason not to do > this? ArchLinux used to ship a Qt4 compiled without support for exceptions years ago, but I remember this caused trouble for me at the time (so can cause for other ISV as well) when I was using the QUndoCommand related classes and my classes inherited from QUndoCommand could throw exceptions on QUndoCommand::redo() if the command fail to execute, so the exception was throw by my application code when running Qt code (QUndoStack::push) and caused a nice segfault until the packager re-compile the Qt4 package with support for exceptions. > The other option would be to fix the -no-exceptions configure flag to mean > no exceptions, except where they are really needed. > > Lars Regards. Hugo Parente Lima
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
