-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/01/2013 11:41 PM, Michael Pyne wrote: >> 1) Are we sure we want to disable exceptions in libraries released in 2014? >> > 2) What is the _BLBAFASEL_EXCEPTIONS_ENABLED_ preprocessor variable that I >> > can use to implemented the exception- and non-exception based code paths? > KSharedDataCache uses exceptions now. This is only in its own code so as not > to bloat the rest of kdelibs for users who don't want exception support, but > I'd say if it makes your code easier, to go for it. > > AFAIK the only reason to avoid exceptions is an increase in code size, which > doesn't strike me as a strong problem in 2014. But on the other hand it might > still be an issue for embedded platforms, which I'm sure we'd want to support. > > I don't know the defines for it though, sorry.
Thanks, Michael. I get from that that I can enable exceptions for threadweaver without affecting the other libraries. This makes my job a lot easier. If there are any concerns with this, please let me know. Since threadweaver jobs execute user code, it needs to at least be able to avoid blowing up. Cheers, Mirko. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJ0ViEACgkQYSSaITCTnKU56wCgj+Vv0PMV8As8Q0R5br7vKZNr n+QAniHmicfAi4AtDuCAdECzRiW3FSDz =2A7/ -----END PGP SIGNATURE----- _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
