Even gcc / Linux has some issues with exceptions across shared library boundaries. They're related to symbol visibility and how exceptions classes are exported in each library in the stack trace. Such issues are also no fun tracking down...
Cheers, João ________________________________________ From: [email protected] [[email protected]] On Behalf Of ext Ivan Cukic [[email protected]] Sent: 27 June 2011 10:22 To: [email protected] Subject: Re: [Qt5-feedback] Qt5 and C++ exception On Monday, 27. June 2011. 12.11.21 Дмитрий Б. wrote: > I very much respect your opinion, but there is a part of community who > believe that exceptions is very important. In addition it is one of the > standard of the C++ which Qt does not support on the API level and it > is a standard for any object-oriented library at all. While I generally like the concept of exceptions, those are quite tricky with c++. As Lars pointed out, dynamic libs and exceptions don't really mix well on some platforms (for example, mixing msvc and gcc compiled exception- enabled code will result in a unique kind of hell :) ) I'm not aware of non-windows os problems, but even if so, a large portion of Qt users are on that platform. Cheerio -- There is a better way of life and it's not so hard to find If you live and let the people in your world speak its mind -- Deep Purple _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
