>> One less copy than returning a "DispatchResult const &" ? >> >> I think we think the same.. ;) > >No, I am wondering why it has to be const. >
Because there is no reason to make it non-const. I can't think of a reason to allow code from outside the Cursor class to change the result of the Cursor dispatching machinery. If something can be const, it's better to make it a const, right ? Vincent
