examples/step-1: Remove explicit reset_manifold

We have restructured our internal manifold handling and the explicit
call to reset_manifold is not necessary any more. (Indeed the
description why this reset is necessary is now factually wrong.) Let's
not confuse the unsuspecting user and remove this part.

Thanks to Mateusz Marciniak for pointing this out.

diff --git a/examples/step-1/step-1.cc b/examples/step-1/step-1.cc
index 3c29516d88d828d0fc9d8362e13ef4cd9a8e623b..a753e1859b91eff621a397c1571584fa79ab15b0 100644 (file)
--- a/examples/step-1/step-1.cc
+++ b/examples/step-1/step-1.cc
@@ -245,21 +245,6 @@ void second_grid()
   grid_out.write_eps(triangulation, out);
 
   std::cout << "Grid written to grid-2.eps" << std::endl;
-
-  // At this point, all objects created in this function will be destroyed in
-  // reverse order. Unfortunately, we defined the manifold object after the
-  // triangulation, which still has a pointer to it and the library will
-  // produce an error if the manifold object is destroyed before the
-  // triangulation. We therefore have to release it, which can be done as
-  // follows. Note that this sets the manifold object used for part "0" of the
-  // domain back to a default object, over which the triangulation has full
-  // control.
-  triangulation.reset_manifold(0);
-  // An alternative to doing so, and one that is frequently more convenient,
-  // would have been to declare the manifold object before the triangulation
-  // object. In that case, the triangulation would have let lose of the
-  // manifold object upon its destruction, and everything would have been
-  // fine.
 }