I've completed the namespaces and headers split step. GEOS namespaces now reflect JTS packages, and all classes are named after JTS classes/interfaces. There are now duplicated names, but in different namespaces (as it is for JTS).
Most client apps will just use the 'geos::geom', 'geos::io' and 'geos::util' namespaces and also not all classes from them. This opens up a chance to reduce exposed API by only installed "maintained" interfaces. We attempted at doing this from the start by providing a geos.h header, including a minimal set of internal headers. We could now reduce that minimal set. What do you think ? Note that the original "catch-all" headers have been currently retained, as a convenience to allow existing application to build w/out much modification. As an example, qgis still builds w/out modifications against GEOS-HEAD. --strk; /"\ ASCII Ribbon Campaign \ / Respect for low technology. X Keep e-mail messages readable by any computer system. / \ Keep it ASCII. _______________________________________________ geos-devel mailing list [EMAIL PROTECTED] http://geos.refractions.net/mailman/listinfo/geos-devel
