Hi Mikhail,
For classes, functions and etc. you can make them protected/private,
for API, the header file can be split into public API part and internal
part.
May be some definitions can be placed into the source (cpp) files.
Also Even mentioned CPL_DLL macro which exported classes/functions from
dll, it should be removed for internal classes/functions.
Best regards,
Dmitry
24.03.2015 20:42, Mikhail Gusev пишет:
Hello all.
I'm trying to fix issues which were mentioned before in order to
integrate GNM into GDAL 2.0. My question is about that issue:
Even Rouault:
- gnm/frmts/gnm_frmts.h : I'm a bit concerned about exposing
(installed
header + CPL_DLL) an interface that has not yet been implemented.
My intuition
is that it might change once the first one or two implementations
have been
made. So maybe keep it internal/experimental for now.
What's the correct way to mark some parts of GNM as internal? Just
write in comments and documentation "this is for internal use for now"
+ not to add the headers to the "install" target, or I need something
else to achieve this?
_______________________________________________
gdal-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/gdal-dev
