Howard Butler wrote: > Mateusz, > > I am working through implementing spatial indexing strategies for libLAS > using http://research.att.com/~marioh/spatialindex/ Its development > requires the addition of a number of indexing-related classes like > LASIndex, LASIndexDataStream, and LASIndexVLRStorage. I could do the > following: > > - put them all in one lasindex.{cpp|hpp} file (breaks our existing > convention) > - put them in separate files in ./src and ./include (a bit messy) > - put them in separate files in a directory ./src/index/vlrstorage.cpp > ./include/index/datastream.hpp (a bit tedious) > > Which is preferable to you? These are public APIs that C++ users would > need to use, so it doesn't make sense that they would be in ./detail.
Yes, if the index stuff belongs to public API, then it should go straight to ./include, but not to ./detail. I mean, that's basically the idea of this include vs detail structure. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net Charter Member of OSGeo, http://osgeo.org _______________________________________________ Liblas-devel mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/liblas-devel
