is there any point to setting up a naming convention for C++ header files?
currently we have a few that are named .hpp (the convention I gather was proposed by the Boost folks), and a bunch named .h. that makes it seem like it's just the whim of the programmer which to use. In some cases it's vaguely confusing: we have rd_client.h which is for everyone and RDClient.h which is just for c++, and which includes rd_client.h. -- mats P.S. this is the list that does use .hpp at the moment: resource/oc_logger/include/oc_log_stream.hpp resource/oc_logger/include/oc_logger.hpp resource/oc_logger/include/oc_log.hpp resource/include/OCProvisioningManager.hpp resource/include/OCCloudProvisioning.hpp service/easy-setup/mediator/richsdk/inc/EasySetup.hpp _______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
