You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
While encapsulating eRPC in a more transport-agnostic object, that can be instantiated multiple times (i.e.: multiple UARTs), there is no way to associate the error handler to a specific instance, since the handler does not support a context. Or, in other words, it is not possible to reuse the same error handler for multiple connections.
Describe the solution you'd like
Add a second parameter while registering the error handler function and pass it when calling such function.
Describe alternatives you've considered
Implementing some black magic using templates and static hash maps to provides a function table. See:
Is your feature request related to a problem? Please describe
While encapsulating eRPC in a more transport-agnostic object, that can be instantiated multiple times (i.e.: multiple UARTs), there is no way to associate the error handler to a specific instance, since the handler does not support a context. Or, in other words, it is not possible to reuse the same error handler for multiple connections.
Describe the solution you'd like
Add a second parameter while registering the error handler function and pass it when calling such function.
Describe alternatives you've considered
Implementing some black magic using templates and static hash maps to provides a function table. See:
Steps you didn't forgot to do
The text was updated successfully, but these errors were encountered: