22 Feb
2016
22 Feb
'16
12:05 a.m.
On 2016-02-21 23:15, Chris Glover wrote: [snip]
This is starting to look a little nasty to me so I'm wondering if anyone has any thoughts on this? Should I stop worrying about it and just use the #ifdef?
I think so, yes. I would just use an #ifdef. The problem with these macros (for me, at least) is that it's not clear what the actual error handling is supposed to be in case if exceptions are disabled. I mean, if you want the code to support the "no exceptions" case, you should design the interfaces with a different method of communicating failures, and simply removing try/catch/throw does not cut it.