From afd5f0efc68cd6de0bc463f7cc59eeee8f32463f Mon Sep 17 00:00:00 2001 From: David Williams Date: Thu, 16 May 2013 08:37:50 +0000 Subject: [PATCH] ErrorHandling.rst edited online with Bitbucket - Just a test commit to see if code copy-and-pastedfrom the BitBucket docs actually shows up in the user manual. --- documentation/ErrorHandling.rst | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/documentation/ErrorHandling.rst b/documentation/ErrorHandling.rst index 829f0563..8b76615c 100644 --- a/documentation/ErrorHandling.rst +++ b/documentation/ErrorHandling.rst @@ -44,4 +44,10 @@ Most functions in PolyVox will validate their input parameters and throw an exce The most notable example of this is when accessing volume data through the get/setVoxel() functions, as these are designed to be very fast. Validating an input position would require multiple conditional operations which we chose to avoid. Therefore, **accessing a voxel outside of a volume will cause undefined behaviour.** When reading voxels it is safer to use the function getVoxelWithWrapping() as this lets you specify how out-of-bounds voxels should be handled. -In addition to the C++ exception handling mechanism, PolyVox also makes use of assertions to verify the internal state of the library at various points. If you hit an assert in PolyVox then there is a good chance it is a bug in the library, as user errors should have been prevented by throwing an exceptions. \ No newline at end of file +In addition to the C++ exception handling mechanism, PolyVox also makes use of assertions to verify the internal state of the library at various points. If you hit an assert in PolyVox then there is a good chance it is a bug in the library, as user errors should have been prevented by throwing an exceptions. + +.. sourcecode :: python + + def wiki_rocks(text): + formatter = lambda t: "funky"+t + return formatter(text) \ No newline at end of file