|Re: [paho-dev] Using C++ with the Paho C client library|
I agree about the timing. The question would be when to fit in the work of:1) which of the parameters, elements of structures, etc to apply the change to. Could be >50 parameters and elements to review.
2) whether to apply the change to #defines as well. I seem to remember starting with const definitions, running into problems again, and hence deciding to go with old-fashioned #defines. This would seem to be more a C++ concern, and can be fixed in a C++ header anyway.
3) testing the implications on all main platform combinations, including back to gcc 3.8 and older MS C/C++ compilers, for effects and backward compatilbility.
Ian On 16/05/13 22:15, Roger Light wrote:
Hi,(2) Observe proper const-ness for pointer parameters if there is no intent in updating the item, particularly "const char*" for "char*" DLLExport int MQTTAsync_create(MQTTAsync* handle, const char* serverURI, const char* clientId, ...It occurs to me that if this change is going to be made (and I'd agree with it) it ought to be done sooner rather than later because it represents an API change. Once there's a proper release and it is being packaged it's a lot more awkward to change. Cheers, Roger _______________________________________________ paho-dev mailing list paho-dev@xxxxxxxxxxx http://dev.eclipse.org/mailman/listinfo/paho-dev
Back to the top