Datapool Updates, fixes and improvements #334
No reviewers
Labels
No Label
API Change
Breaking API Change
bug
build
cosmetics
Documentation
duplicate
feature
help wanted
hotfix
invalid
question
Refactor
Tests
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: fsfw/fsfw#334
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "mueller/datapool-update"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Also, new RAII conformant reader class to read and commit to datapool variables and datasets.
A few questions:
setReadCommitProtectionBehaviour is ment to be called by the user in LocalDataPoolManager? Who wants to call that? Who doesn't?
@ -39,3 +41,3 @@
result = readVariable(count);
if(result != RETURN_OK) {
break;
error = result;
This reports only the last error in the loop. Is any value valid in the set after reading one with an error? We still don't know where the error happened.
@ -112,3 +129,3 @@
&& registeredVariables[count]->getDataPoolId()
!= PoolVariableIF::NO_PARAMETER) {
registeredVariables[count]->commitWithoutLock();
if(protectEveryReadCommitCall) {
"protectEveryReadCommitCall" but this is a write call.
@ -0,0 +19,4 @@
//! members with commit and read semantics where the lock is only necessary
//! once.
virtual ReturnValue_t readWithoutLock() {
return read(20);
I don't get that. This looks like a call with a lock with a fixed 20 (ms) timeout.