patacongo edited a comment on pull request #415: URL: https://github.com/apache/incubator-nuttx-apps/pull/415#issuecomment-702749975
> We can version the structure if you think it is necessary. Or the user can use the Non binary version until you make it perfect. We are not designing code here. But my thought was to put two different binary structures back-to-back, one for IPv4 and one for IPv6. Either or both could be present. Each would add only: - An byte size offset to the next structure (zero meaning the end of the list) - An byte-size identifier to identify the type of structure IPv4 or IPv6 This would eliminate the "explosive growth". If we were to add those two bytes to the beginning of the structure now (both set to zero and type == 0 meaning IPv4), then we would have binary backward compatibility in the future. No versioning is really needed. The ipcfg_read() interface would change in that you would requires an address family type as an additional argument. The cost of these two additional bytes is zero since there will be three bytes lost to padding in the first four bytes anyway. We freeze 10.0 tomorrow. There is no time to road test any significant changes now. None at all. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
