From 5f7d0f1aea382923f13f40a660f1ce36cf42b4ea Mon Sep 17 00:00:00 2001 From: Wolfgang Bangerth Date: Sat, 26 Oct 2013 12:49:12 +0000 Subject: [PATCH] Fix up comment. git-svn-id: https://svn.dealii.org/trunk@31442 0785d39b-7218-0410-832d-ea1e28bc413d --- deal.II/examples/step-32/step-32.cc | 37 ++++++++++++++++------------- 1 file changed, 20 insertions(+), 17 deletions(-) diff --git a/deal.II/examples/step-32/step-32.cc b/deal.II/examples/step-32/step-32.cc index c993c97868..99c18dc75e 100644 --- a/deal.II/examples/step-32/step-32.cc +++ b/deal.II/examples/step-32/step-32.cc @@ -2179,23 +2179,26 @@ namespace Step32 // i.e., it returns true exactly if the cell is owned by the current // processor. The resulting iterator range is then exactly what we need. // - // With this obstacle out of the way, we call the WorkStream::run function - // with this set of cells, scratch and copy objects, and with pointers to - // two functions: the local assembly and copy-local-to-global - // function. These functions need to have very specific signatures: three - // arguments in the first and one argument in the latter case (see the - // documentation of the WorkStream::run function for the meaning of these - // arguments). Note how we use the construct std_cxx1x::bind - // to create a function object that satisfies this requirement. It uses - // placeholders _1, std_cxx1x::_2, _3 for the local assembly - // function that specify cell, scratch data, and copy data, as well as the - // placeholder _1 for the copy function that expects the data - // to be written into the global matrix. On the other hand, the implicit - // zeroth argument of member functions (namely the this pointer - // of the object on which that member function is to operate on) is - // bound to the this pointer of the current - // function. The WorkStream::run function, as a consequence, does not need - // to know anything about the object these functions work on. + // With this obstacle out of the way, we call the WorkStream::run + // function with this set of cells, scratch and copy objects, and + // with pointers to two functions: the local assembly and + // copy-local-to-global function. These functions need to have very + // specific signatures: three arguments in the first and one + // argument in the latter case (see the documentation of the + // WorkStream::run function for the meaning of these arguments). + // Note how we use the construct std_cxx1x::bind to + // create a function object that satisfies this requirement. It uses + // placeholders std_cxx1x::_1, std_cxx1x::_2, + // std_cxx1x::_3 for the local assembly function that specify + // cell, scratch data, and copy data, as well as the placeholder + // std_cxx1x::_1 for the copy function that expects the + // data to be written into the global matrix. On the other hand, the + // implicit zeroth argument of member functions (namely the + // this pointer of the object on which that member + // function is to operate on) is bound to the + // this pointer of the current function. The + // WorkStream::run function, as a consequence, does not need to know + // anything about the object these functions work on. // // When the WorkStream is executed, it will create several local assembly // routines of the first kind for several cells and let some available -- 2.39.5