On quarta-feira, 11 de janeiro de 2017 19:41:09 PST Pawel Winogrodzki wrote: > If the C++ APIs may be modified with disregard to backwards compatibility, > then I should be able to switch OCRepresentation to use int64_t as the only > supported integer type and thus be compatible with the rest of the code. > > I would need to know, if there is a IoTivity-wide approval to perform such > changes, before I start working on them.
In my opinion, it should. The distinction between the C and the C++ API exists for reasons that are no longer valid. The C API is too low-level to the point of being obfuscated, like a function "do" that takes 9 parameters, while the C++ API is too high level and does not get enough attention, not to mention that it was designed with intentional disregard for compatibility with older, non-C++11 compilers. We should have a unified API in one language only -- I understand Microsoft's preference would be for a C API. We do need an IoTivity-wide approval for replacement, but we can start adding one meanwhile, intermediate to the existing two, and leave the approval to when it's complete and can show its own benefits. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
