How to delegate an action to function return?

  • A+

The problem

I have the following simple situation popping up all over the place. A large number of requests come to the device with a function signature like this:

Err execute( const ICommandContext &context,           const RoutineArguments &arguments,           RoutineResults &results) 

There is essentially a request handling server that will call this execute the function for a variety of request types that have these signatures. We have 2 return paths in the case of an error.

  1. The Err output type (consider it to be equivalent to an int) which is used to inform the server or system that something has gone wrong that is to do with the system, not the request. This is always sorted at the top of the function before the user request is dealt with.
  2. RoutineResults provides a setStatus function that can be used to return failure information of the request to the client.

For this reason we have a lot of this type of code popping up:

// Failure due to request Err error = someFunctionCall(clientInput); if (!error.success()) {     results.setStatus(error); // Inform the client of the error     return SUCCESS; // Inform the system that we are all good } 

We have a particular request type that has around 15 parameters that come in and are sent off around the system. We would conceptually need 15 of this if error do set which seems wasteful. It is also prone to errors if we need to go through and change anything about how we return. How can we effectively delegate the setStatus and return to a short amount of code that only needs to happen once in the function?

A Macro Solution

A c system might solve this with a macro, something like:

#define M_InitTry Err error #define M_Try(statement) if (!(error = statement).success()) { goto catch_lab; } #define M_Catch catch_lab: if (!error.successs()) #define M_Return return error 

Which would be used like this:

Err execute( const ICommandContext &context, ...) {     M_InitTry;      ...      M_Try(someFunctionCall(clientInput));     M_Try(someFunctionCall(otherClientInput));     ...      M_Catch {         // Other specific actions for dealing with the return.         results.setStatus(error);         error = SUCCESS;     }     M_Return; } 

This cleans the code nicely, but is not particularly nice with the goto. It will cause problems if defining variables that might be skipped by a goto.

A delegating solution

I was trying to think of a more C++ so I thought an RAII type delegate might help. Something like:

class DelegateToFunctionEnd {      typedef std::function<void(void)> EndFunction;       public:      DelegateToFunctionEnd(EndFunction endFunction) : callAtEnd(endFunction) { }      ~DelegateToFunctionEnd() {         callAtEnd();     }      private:              EndFunction callAtEnd; }; 

Pretty simple, it does a delegate of the action until the function return by implementing the action in the destructor. You might use it like this:

Err execute( const ICommandContext &context, ...) {     Err error;     DelegateToFunctionEnd del(std::bind(&RoutineResults::setStatus, &results, std::cref(error)));      error = someFunctionCall(clientInput));     if (error) return SUCCESS;      ... } 

Live example. This solution seems ok, but has several problems:

  1. It is not as clear what is happening.
  2. It is easier to make a mistake about setting error correctly.
  3. You still need a large number of if statements to deal with the returns.
  4. The ability to configure the terminating action is not great.
  5. Dangerous if the user doesn't carefully consider the destruction order of items at function return.

A better solution?

This must be a problem that comes up often. Is there a general solution that provides a clean delegation of this set and returns type action?

I have some unfortunate restrictions below. Don't let these stop you from answering because it might be helpful for future people.

  1. I am working on a c++03 limited system. We have boost, but no c++11.
  2. Embedded system and we have silly rules about exceptions and memory allocation.


If error status codes are proving troublesome, you should consider using exceptions instead. That is, change the API of your functions

  • so they are guaranteed to have success as a post-condition
  • throw a suitable std::exception in the event of failure

It is impossible to "forget" to examine a status code if you do this. If you choose not to handle an error condition, the exception thrown by low-level code automatically percolates upwards. You only need to catch a low-level exception if

  • You need to do some manual roll-back or deallocation in the event of an error, and RAII is impractical. In this case you would rethrow the expcetion.
  • You want to translate a low-level exception message or exception type into a high-level message, using a thrown) nested exception.


:?: :razz: :sad: :evil: :!: :smile: :oops: :grin: :eek: :shock: :???: :cool: :lol: :mad: :twisted: :roll: :wink: :idea: :arrow: :neutral: :cry: :mrgreen: