On 02/27/2018 12:24 AM, Thiago Macieira wrote:
On segunda-feira, 26 de fevereiro de 2018 14:26:12 PST Philippe Coval wrote:
I remember I renamed some C++ headers to .hpp suffix
because filenames were clashing on case insensitive FS
We can rename those few again,
but make sure it's not create ambiguity.
Naming C++ source files as .C and headers as .H hasn't been done in three
decades...
Sure but some filesystems don't like it,
Some conventions I used before:
.hpp for regular c++ header (and .hxx for c++ templates)
For the record:
https://gerrit.iotivity.org/gerrit/14747
https://gerrit.iotivity.org/gerrit/#/c/16479/
commit d646926ebdf6d2621e156b8ac7b8ddb2ca8dce36
Author: Philippe Coval <[email protected]>
Date: Thu Nov 24 11:20:23 2016 +0100
provisioning: Rename some C++ headers to avoid collision with CSDK ones
The name clash only happens
on case insensitive filesystems (ie HPFS on MacOS),
there is ambiguity with C header ie:
./resource/csdk/security/provisioning/include/ocprovisioningmanager.h
./resource/include/OCProvisioningManager.h
Renaming to .hpp suffix prevent the problem.
Note, one other approach would be to use namespaces
Like:
#include <iotivity/csdk/ocprovisioningmanager.h> vs
#include <iotivity/oc/ocprovisioningmanager.h> or similar
--
mailto:[email protected] gpg:0x467094BC
https://blogs.s-osg.org/author/pcoval/
_______________________________________________
iotivity-dev mailing list
[email protected]
https://lists.iotivity.org/mailman/listinfo/iotivity-dev
