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
For now since we are only dealing with CBOR and CoAP, we don't need to worry too much.
But when we want to start adding support for other language besides C, we would want to create an intermediate json file that would contain the generated variable/enum names.
This is because the logic of converting the csv table names into variable/enum name would be the common factor between two different language header conversions.
This would however make it not a single python program operations, but rather two. First one to convert from IANA csv files to our internal json representation, then the second program would read it and then generate the language specific code (along with the relevant backward compatibility handling that would be needed for each project).
The text was updated successfully, but these errors were encountered:
For now since we are only dealing with CBOR and CoAP, we don't need to worry too much.
But when we want to start adding support for other language besides C, we would want to create an intermediate json file that would contain the generated variable/enum names.
This is because the logic of converting the csv table names into variable/enum name would be the common factor between two different language header conversions.
This would however make it not a single python program operations, but rather two. First one to convert from IANA csv files to our internal json representation, then the second program would read it and then generate the language specific code (along with the relevant backward compatibility handling that would be needed for each project).
The text was updated successfully, but these errors were encountered: