On 2013-11-02, Mirko Boehm wrote:
> I get from that that I can enable exceptions for threadweaver without
> affecting the other libraries. This makes my job a lot easier.
note though that most of Qt isn't really compatiple with exceptions. see
also long threads on qt-dev list.
/Sune
__
> > 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
Modern compilers tend to work very well with exceptions if those are used only
for error branches and not as goto statements :)
> If there are any
-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 no
On Fri, November 1, 2013 17:30:02 Mirko Boehm wrote:
> Hi,
>
> in ThreadWeaver, I would like to be able to catch exceptions thrown from the
> run() method of Jobs. You know we cannot trust the user :-) I can work
> around if exceptions are disabled in the compiler if I know about it. What
> I woul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
in ThreadWeaver, I would like to be able to catch exceptions thrown from the
run() method of Jobs. You know we cannot trust the user :-) I can work around
if exceptions are disabled in the compiler if I know about it. What I would
like to be a