Go to the source code of this file.
|
class | ucam::util::Runner< SingleThreadedFunctorT, MultiThreadedFunctorT > |
| Convenience wrapper class that can kick off two type of executions: singlethreaded or multithreaded, triggered by program options. Possibly multithreading with 1 thread would do, but I keep both implementations as any plain bug that might arise will be easier to trace down with a normal execution (threadpool uses two, actually). The class is templated with two classes, one for single threading and another for multithreading. Note that the multithreading details are up to the second templated class. e.g. Runner<SingleThreadedFunctor,SingleThreadedFunctor> would not multithread at all ;-). More...
|
|
class | ucam::util::Runner2< SingleThreadedFunctorT, MultiThreadedFunctorT > |
| Convenience wrapper class that can kick off two type of executions: single or multithreaded, triggered by program options. Possibly multithreading with 1 thread would do, but I keep both implementations as any plain bug that might arise will be easier to trace down with a serialized execution (threadpool uses two, actually). The class is templated with two classes, one for single threading and another for multithreading. Note that the multithreading details are up to the second templated class. More...
|
|
class | ucam::util::Runner3< SingleThreadedFunctorT, MultiThreadedFunctorT, ServerFunctorT > |
| Convenience wrapper class that can kick off three type of executions: singlethreaded, multithreaded, or server, triggered by program options. Possibly multithreading with 1 thread would do, but I keep both implementations as any plain bug that might arise will be easier to trace down with a single thread execution. The class is templated three functors, one for each type of execution Note that the details are up to the each of these functors. More...
|
|