diff options
Diffstat (limited to 'lib')
| -rw-r--r-- | lib/talloc/doc/tutorial_context.dox | 10 | ||||
| -rw-r--r-- | lib/talloc/doc/tutorial_dts.dox | 6 |
2 files changed, 8 insertions, 8 deletions
diff --git a/lib/talloc/doc/tutorial_context.dox b/lib/talloc/doc/tutorial_context.dox index 593c15c83f..b8bfe26961 100644 --- a/lib/talloc/doc/tutorial_context.dox +++ b/lib/talloc/doc/tutorial_context.dox @@ -164,11 +164,11 @@ struct user *user_zero = talloc_zero(ctx, struct user); The zero-length context is basically a context without any special semantical meaning. We can use it the same way as any other context. The only difference is that it consists only of the meta data about the context. Therefore, it is -strictly of type |TALLOC_CTX*|. It is often used in cases where we want to -aggregate several data structures under one parent (zero-length) context, such -as a temporary context to contain memory needed within a single function that -is not interesting to the caller. Allocating on a zero-length temporary context -will make clean-up of the function simpler. +strictly of type <code>TALLOC_CTX*</code>. It is often used in cases where we +want to aggregate several data structures under one parent (zero-length) +context, such as a temporary context to contain memory needed within a single +function that is not interesting to the caller. Allocating on a zero-length +temporary context will make clean-up of the function simpler. @code TALLOC_CTX *tmp_ctx = NULL; diff --git a/lib/talloc/doc/tutorial_dts.dox b/lib/talloc/doc/tutorial_dts.dox index 62c425c408..75b5172bbe 100644 --- a/lib/talloc/doc/tutorial_dts.dox +++ b/lib/talloc/doc/tutorial_dts.dox @@ -6,8 +6,8 @@ Generic programming in the C language is very difficult. There is no inheritance nor templates known from object oriented languages. There is no dynamic type system. Therefore, generic programming in this language is usually done by -type-casting a variable to |void*| and transferring it through a generic function -to a specialized callback as illustrated on the next listing. +type-casting a variable to <code>void*</code> and transferring it through +a generic function to a specialized callback as illustrated on the next listing. @code void generic_function(callback_fn cb, void *pvt) @@ -45,7 +45,7 @@ Although the name of the context can be set to any arbitrary string, the best way of using it to simulate the dynamic type system is to set it directly to the type of the variable. -It is recommended to use one of |talloc()| and |talloc_array()| (or its +It is recommended to use one of talloc() and talloc_array() (or its variants) to create the context as they set its name to the name of the given type automatically. |