From: Wolfgang Bangerth Date: Mon, 26 Jun 2000 09:33:05 +0000 (+0000) Subject: Fix "@p NULL" by "@p{Null}" X-Git-Tag: v8.0.0~20353 X-Git-Url: https://gitweb.dealii.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=76e5e4c7a44dea6add7df1e73c68531b1e11a60f;p=dealii.git Fix "@p NULL" by "@p{Null}" git-svn-id: https://svn.dealii.org/trunk@3070 0785d39b-7218-0410-832d-ea1e28bc413d --- diff --git a/deal.II/deal.II/include/grid/tria.h b/deal.II/deal.II/include/grid/tria.h index b3592e646e..fe23a3ae53 100644 --- a/deal.II/deal.II/include/grid/tria.h +++ b/deal.II/deal.II/include/grid/tria.h @@ -1141,7 +1141,7 @@ struct TriaNumberCache<3> : public TriaNumberCache<2> * line, quad, etc. You can access these user pointers through the * functions @p{user_pointer()}, @p{clear_user_pointer()} and * @p{set_user_pointer(p)} in the accessor classes. These pointers are - * neither used nor changed by the library and are @p NULL by + * neither used nor changed by the library and are @p{NULL} by * default. Thus, their handling is the sole responsibility of the * application program. Especially, the pointers are not inherited * to children upon refinement. Still, after a remeshing they are