Allow custom transport and MAC constructor arguments #159
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the current buildTransportWithAdapter and buildMACLayer_T functions
you are limited to only passing in NEMId, PlatformServiceProvider* and RadioServiceProvider* (MAC) as constructor params for a custom transport or MAC layer.
This change uses a parameter pack to allow an arbitrary number of
arguments to be passed to the transport/MAC constructor. And by using
perfect forwarding there should be no additional cost in copying those
params to the transport instance.
For example, with this change you can do something like this:
See also this change. I don't intend to merge this, but used it to test the change to buildMACLayer_T.
bobmourlam/emane-embedded-example@3147d0f?w=1
Signed-off-by: Bob Mourlam bob.mourlam@gmail.com