HomePhorge

Implemented CrossReliability Functionality

Referenced Files
None
Subscribers

Description

Implemented CrossReliability Functionality

Cleared up the misunderstanding
implemented the CrossReliability Correctly
ToDo: Document

Details

Provenance
danielAuthored on May 2 2019, 12:55 PM
dschnoellPushed on May 2 2019, 4:02 PM
Parents
R20:43f9eab48272: adapded to Benedikts Linear Function s
Branches
Unknown
Tags
Unknown

Event Timeline

daniel <daniel.s13@live.de> committed R20:b3bad676be0b: Implemented CrossReliability Functionality (authored by daniel <daniel.s13@live.de>).May 2 2019, 1:52 PM
juhasz added inline comments.
/include/rosa/agent/CrossReliability.h
100

It would be more flexible to store an std::function rather than a raw function pointer.

If flexibility is not required (for example, only a small number of pre-defined functions are expected as actual parameters), then it is better to restrict the possible input values: the parameter should be some kind of identifier for the method, for which the function stores the corresponding function pointer in the Method field.

If an arbitrary function should be accepted as Method, I suggest to use std::function, which allows much more options for the user code to set Method (e.g., lambda expressions, bind expressions, member functions).