From 01d2279540d91044d513f21c9a7bfb09bac1e22e Mon Sep 17 00:00:00 2001 From: Timo Heister Date: Thu, 24 Oct 2019 11:09:04 +0200 Subject: [PATCH] take over changes from 17f331bb57 --- examples/step-12b/step-12b.cc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/examples/step-12b/step-12b.cc b/examples/step-12b/step-12b.cc index 8aac1461b7..5c02885ecd 100644 --- a/examples/step-12b/step-12b.cc +++ b/examples/step-12b/step-12b.cc @@ -203,7 +203,7 @@ namespace Step12 // pointers to these functions to the MeshWorker framework. If, however, // these functions would want to access member variables (or needed // additional arguments beyond the ones specified below), we could use the - // facilities of boost::bind (or std::bind, respectively) to provide the + // facilities of lambda functions to provide the // MeshWorker framework with objects that act as if they had the required // number and types of arguments, but have in fact other arguments already // bound. @@ -312,7 +312,7 @@ namespace Step12 // integrator class are not actually function pointers. Rather, they are // objects that can be called like functions with a certain number of // arguments. Consequently, we could also pass objects with appropriate - // operator() implementations here, or the result of std::bind if the local + // operator() implementations here, or lambda functions if the local // integrators were, for example, non-static member functions. MeshWorker::loop