Error handling policies about ponder HOT 3 CLOSED

But then what would happen if you put asserts in? You'd get the same result, and no way to catch the error and perhaps recover.

You can put a try-catch handler at a high level point in your code after which point you use Ponder. If you are getting any exceptions it is because there is a bug in your app logic or type registration, e.g. a wrong name etc. Here you can print out the exception details and fix it.

I haven't use gdb for a long time and I can't remember how it works. You might try the free Visual Studio 2015 offering. Not a bad IDE for free.

from ponder.

I'm going to close this for now as I think exceptions is the right solution for now. The main downside is performance of them, but they just shouldn't be firing unless there is a bug, which will need fixing.

from ponder.

Firstly, thank you for all the other enhancements. I haven't tried them yet but will do soon.

I am working on Linux so a bit stuck with gdb, but anyway this is certainly something I can live with given all the other great things about Ponder.

All the 'Ponder heavy' sections are now wrapped in try .. catch, it's just the odd Value::To<> one liners like:

int length = uLength.To<int>();

where I would prefer to assert - and fix - rather than wrap every one in try .. catch.

Having said that, the beauty of open source is that I can always look at replacing PONDER_ERROR with my own version in my local copy :)

from ponder.