Closed tim-griesbach closed 1 month ago
Sounds good! Do we have a way to indicate in the code very clearly which parts are collective and which are not? This seems very important for the parallel consistency of error checking. Maybe by means of extra function calls into non-collective paths with proper naming? "Just" comments and conventions may not be sufficiently safe.
The non-collective code paths are already in separate functions and the current naming convention for these static functions is that their name ends with _internal
. I could replace the current name endings by _serial
to be more clear on the functions' purpose.
scda: Fuzzy error synchronization and padding optimization
This PR continues the implementation of the scda file format (cf. https://github.com/cburstedde/libsc/pull/201) by adding two smaller changes.
sc_scda_check_pad_to_fix_len
to check fixed-length padding without extracting the raw data. This function enables more modularization, saves one unnecessary copy of the vendor string and makes the set of padding functions for both padding options symmetric.