On Tue, Dec 6, 2022, 8:04 PM Daniel Baston <dbas...@gmail.com> wrote:
> Hi All, > > The "Priority 1" item in this list has been completed, and I've been > chipping away at items #3 and #5 as well as many bug fixes and > opportunistic optimizations. While there is plenty to keep busy with along > this track, I want to be responsive to the needs of the broader GEOS > community. If you are using GEOS in your application or library, please be > a squeaky wheel and create GitHub issues with your requests (or reply to > this email.) > > I'm particularly interested in some feedback on the "defining a C++ API" > item, which is now ticketed at https://github.com/libgeos/geos/issues/755. > Does anyone have an example of a library that has a good system for > designating stable methods while allowing continual changes in the > internals? > Do you build a shared library? If so, limit what you export to what you want to be your API. Don't document anything else. Maybe I'm missing something in what you're asking.
_______________________________________________ geos-devel mailing list geos-devel@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/geos-devel
