From 16a2d896bc77f42102fef5f6407a4eb64cb4b62d Mon Sep 17 00:00:00 2001 From: Tim Holy Date: Mon, 20 Jun 2011 22:47:58 -0500 Subject: Relatively straightforward changes to wording of documentation, focusing particularly on the sparse and (to a lesser extent) geometry pages. --- doc/C07_TutorialReductionsVisitorsBroadcasting.dox | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/C07_TutorialReductionsVisitorsBroadcasting.dox') diff --git a/doc/C07_TutorialReductionsVisitorsBroadcasting.dox b/doc/C07_TutorialReductionsVisitorsBroadcasting.dox index 44e963424..e58ff6e2c 100644 --- a/doc/C07_TutorialReductionsVisitorsBroadcasting.dox +++ b/doc/C07_TutorialReductionsVisitorsBroadcasting.dox @@ -93,7 +93,7 @@ Array. The arguments passed to a visitor are pointers to the variables where the row and column position are to be stored. These variables should be of type -\link DenseBase::Index Index \endlink (FIXME: link ok?), as shown below: +\link DenseBase::Index Index \endlink, as shown below: @@ -141,7 +141,7 @@ return a 'column-vector' \subsection TutorialReductionsVisitorsBroadcastingPartialReductionsCombined Combining partial reductions with other operations It is also possible to use the result of a partial reduction to do further processing. -Here is another example that aims to find the column whose sum of elements is the maximum +Here is another example that finds the column whose sum of elements is the maximum within a matrix. With column-wise partial reductions this can be coded as:
Example:Output:
-- cgit v1.2.3