Error handling improvements

Create issue
Issue #15 resolved
David Williams created an issue

PolyVox is a bit of a mess in terms of error handling. We need consitent use of assert vs. return codes vs. exceptions (if any) vs. logging (if any).

Comments (2)

  1. David Williams reporter

    We now have a new POLYVOX_ASSERT and also POLYVOX_THROW which allows exception handling to be disabled. These should be controlled by a new 'config.h' and there should also be a test for the 'throw handler'.

  2. David Williams reporter

    Config.h now exists, but it's very hard to write a meaningful test of the throw handler as tests are built with exceptions enabled. I don't think it's worth trying to fix this, so I'll assume it works and it will probably get tested as part of Cubiquity in the future.

  3. Log in to comment