On 02/27/2018 12:45 AM, Gregg Reynolds wrote:
On Mon, Feb 26, 2018 at 5:33 PM, Philippe Coval
<philippe.co...@osg.samsung.com
<mailto:philippe.co...@osg.samsung.com>> wrote:
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,
Explain please?
...
If FS is not case sensitive, then you'll could have to files seen as
same name,
so it can be dangerous (which one will be included ? first occurence in
include path ?)
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
There are no namespaces in C as I am sure you know. A file path is
not a namespace.
yes not a C++ namespace to put classes in,
but you got my point don't you ?
--
mailto:philippe.co...@osg.samsung.com gpg:0x467094BC
https://blogs.s-osg.org/author/pcoval/
_______________________________________________
iotivity-dev mailing list
iotivity-dev@lists.iotivity.org
https://lists.iotivity.org/mailman/listinfo/iotivity-dev
