From e03babf7d01843a204776182a8dc005907cc84fb Mon Sep 17 00:00:00 2001 From: Inaky Perez-Gonzalez Date: Mon, 13 Jun 2016 15:30:27 -0700 Subject: [PATCH] doc: fix references to examples in variables.rst Files had been changed without the offsets being updated, so it was generating warnings. Change-Id: I5c7756f396cf607470da1ce6c5807e5a343491d2 Signed-off-by: Inaky Perez-Gonzalez --- doc/contribute/doxygen/variables.rst | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/doc/contribute/doxygen/variables.rst b/doc/contribute/doxygen/variables.rst index b70226788b1..befb81c9bcc 100644 --- a/doc/contribute/doxygen/variables.rst +++ b/doc/contribute/doxygen/variables.rst @@ -29,7 +29,7 @@ the best practices. .. literalinclude:: phil_fiber_commented.c :language: c - :lines: 110-168 + :lines: 92-160 :emphasize-lines: 15, 18, 21-23, 25, 31 :linenos: @@ -53,9 +53,8 @@ Example 2 ========= Variables outside of functions must be documented as well. -.. literalinclude:: hello_commented.c - :language: c - :lines: 133-140 +.. literalinclude:: ./hello_commented.c + :lines: 119-127 :emphasize-lines: 1, 4, 7 :linenos: @@ -68,4 +67,4 @@ Notice that the variable comments also apply for more complex types like structs. The comments on lines 4 and 7 apply only to the specific variable and not to the whole struct. Complex types must be documented wherever they are defined. See :ref:`structs` and -:ref:`typedefs` for further details. \ No newline at end of file +:ref:`typedefs` for further details.