Mention PersistantTriangulation.

git-svn-id: https://svn.dealii.org/trunk@21158 0785d39b-7218-0410-832d-ea1e28bc413d

diff --git a/deal.II/deal.II/include/grid/grid_in.h b/deal.II/deal.II/include/grid/grid_in.h
index 79d4ef75f303ed52057b186e6d64df51ab535111..b2dbd8f900bbcf2bd72b4226da499888aad783e4 100644 (file)
--- a/deal.II/deal.II/include/grid/grid_in.h
+++ b/deal.II/deal.II/include/grid/grid_in.h
@@ -38,19 +38,19 @@ class SubCellData;
  * ignored. Notice also that at the moment in the codimension 1 case only UCD
  * and Gmsh format are accepted.
  *
- * Since the coarse mesh fed into a @p Triangulation object cannot
- * have hanging nodes, strange things will happen if the input file
- * has them. This is due to the fact that most mesh description
- * formats do not store neighborship information between cells, so the
- * grid reading functions have to regenerate it. They do so by
- * checking whether two cells have a common face. If there are hanging
- * nodes in a triangulation, adjacent cells have no common face, so
- * the grid reader concludes that the adjacent cells have no neighbors
- * along these faces and must therefore be at the boundary. In effect,
- * an internal crack of the domain is introduced this way. Since such
- * cases are very hard to detect, the library does not make any
- * attempt to abort on such situations, and you will get a
- * triangulation that probably does not do what you want.
+ * Since the coarse mesh fed into a @p Triangulation object cannot have
+ * hanging nodes, strange things will happen if the input file has them. This
+ * is due to the fact that most mesh description formats do not store
+ * neighborship information between cells, so the grid reading functions have
+ * to regenerate it. They do so by checking whether two cells have a common
+ * face. If there are hanging nodes in a triangulation, adjacent cells have no
+ * common (complete) face, so the grid reader concludes that the adjacent
+ * cells have no neighbors along these faces and must therefore be at the
+ * boundary. In effect, an internal crack of the domain is introduced this
+ * way. Since such cases are very hard to detect, the library does not make
+ * any attempt to abort on such situations, and you will get a triangulation
+ * that probably does not do what you want. A solution to this problem is the
+ * PersistantTriangulation class.
  *
  * Note: if you experience unexpected problems with the use of this
  * class, be sure to read the documentation right until the end, and