action helper nullptr check #454

Closed
muellerr wants to merge 2 commits from mueller/action-printout into mueller/restructuring
Owner

Target is #445 for easier comparison now, might be retargeted.

Target is #445 for easier comparison now, might be retargeted.
muellerr added 1 commit 2021-08-06 11:17:14 +02:00
muellerr added the
feature
label 2021-08-06 11:19:54 +02:00
muellerr added this to the v2.0.0 milestone 2021-08-06 11:21:38 +02:00
Owner

Initialize has checked that the pointer is valid before (as is the main purpose of initialize(), checking the settings).

While I agree that forgetting to call initialize() is an annoying and hard to find bug, I am not sure we should enforce it by doing redundant checks throughout the code.

Initialize has checked that the pointer is valid before (as is the main purpose of `initialize()`, checking the settings). While I agree that forgetting to call `initialize()` is an annoying and hard to find bug, I am not sure we should enforce it by doing redundant checks throughout the code.
Author
Owner

I think this was forgotten because it was overriden in the ExtendedControllerBase .. nullptr checks are cheap, so I introduced this because the software crashed without any warning.. but I'm not sure whether it is worth it.. It just improved the capability of the FSFW to catch configuration errors

I think this was forgotten because it was overriden in the `ExtendedControllerBase` .. `nullptr` checks are cheap, so I introduced this because the software crashed without any warning.. but I'm not sure whether it is worth it.. It just improved the capability of the FSFW to catch configuration errors
muellerr added 1 commit 2021-08-09 15:29:04 +02:00
mohr closed this pull request 2021-08-09 15:29:09 +02:00

Pull request closed

Sign in to join this conversation.
No description provided.