struct sRadioInfo is not self explanatory and therefore is hard to maintain.
Farther data constructions (slaves_sockets, slave_iface_socket) built on it makes it even harder to understand and maintain a coherent, once written, debugged code. One must be an expert in this data structure and the constructions on top it to get required information.
Prefferred Situation -
Turn sRadioInfo structure and the structures on top of it into separated, standalone, classes with clear and concise interfaces. Via these interfaces one is able to query any information with a clear and simple function call. All future data queries required from these data structures will be implemented internally, leaving the user unaware of the internal complexity.
Current Situation -
struct sRadioInfo
is not self explanatory and therefore is hard to maintain. Farther data constructions (slaves_sockets, slave_iface_socket) built on it makes it even harder to understand and maintain a coherent, once written, debugged code. One must be an expert in this data structure and the constructions on top it to get required information.Prefferred Situation - Turn
sRadioInfo
structure and the structures on top of it into separated, standalone, classes with clear and concise interfaces. Via these interfaces one is able to query any information with a clear and simple function call. All future data queries required from these data structures will be implemented internally, leaving the user unaware of the internal complexity.