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
The FSWLOGGER switch is used as an indicator to disable interactive mode in a number of utility and test programs; this seems wrong, as in crewed missions there will be flight software that might be operated by humans. A more narrowly targeted explicit switch, something like NON_INTERACTIVE, would be better. Also, when this switch is enabled we additionally need to #ifdef-out any functions that are exclusively invoked by the disable interactive code, e.g., handleQuit.
The text was updated successfully, but these errors were encountered:
The FSWLOGGER switch is used as an indicator to disable interactive mode in a number of utility and test programs; this seems wrong, as in crewed missions there will be flight software that might be operated by humans. A more narrowly targeted explicit switch, something like NON_INTERACTIVE, would be better. Also, when this switch is enabled we additionally need to #ifdef-out any functions that are exclusively invoked by the disable interactive code, e.g., handleQuit.
The text was updated successfully, but these errors were encountered: