aboutsummaryrefslogtreecommitdiffhomepage
path: root/doc/FunctionsTakingEigenTypes.dox
diff options
context:
space:
mode:
authorGravatar Patrik Huber <patrikhuber@gmail.com>2018-07-26 19:55:19 +0000
committerGravatar Patrik Huber <patrikhuber@gmail.com>2018-07-26 19:55:19 +0000
commitf5cace5e9fc734a9f26b9cf14e806bd1b115e443 (patch)
treed22791d2e9c228bd3271cedddace937cd4ecb668 /doc/FunctionsTakingEigenTypes.dox
parent34539c4af4a3534033563767570c0cece35a2332 (diff)
Fix two small typos in the documentation
Diffstat (limited to 'doc/FunctionsTakingEigenTypes.dox')
-rw-r--r--doc/FunctionsTakingEigenTypes.dox2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/FunctionsTakingEigenTypes.dox b/doc/FunctionsTakingEigenTypes.dox
index e054714f9..6b4e49214 100644
--- a/doc/FunctionsTakingEigenTypes.dox
+++ b/doc/FunctionsTakingEigenTypes.dox
@@ -79,7 +79,7 @@ These examples are just intended to give the reader a first impression of how fu
\section TopicUsingRefClass How to write generic, but non-templated function?
-In all the previous examples, the functions had to be template functions. This approach allows to write very generic code, but it is often desirable to write non templated function and still keep some level of genericity to avoid stupid copies of the arguments. The typical example is to write functions accepting both a MatrixXf or a block of a MatrixXf. This exactly the purpose of the Ref class. Here is a simple example:
+In all the previous examples, the functions had to be template functions. This approach allows to write very generic code, but it is often desirable to write non templated functions and still keep some level of genericity to avoid stupid copies of the arguments. The typical example is to write functions accepting both a MatrixXf or a block of a MatrixXf. This is exactly the purpose of the Ref class. Here is a simple example:
<table class="example">
<tr><th>Example:</th><th>Output:</th></tr>