Angus Johnson

Hi. I'm the author of Clipper and the culprit for removing these files from SourceForge's server😱. And my apologies for the inconvenience this has evidently caused. Until the very recent...

> The zips have a top-level dir which I need to remove. Work in progress! OK, once that's done, and I've downloaded these patched files, is there anything special I...

> For now, just restore the 4.10.0 zip from my link above to Older%20versions/clipper_ver4.10.0.zip" OK, it's there [now](https://sourceforge.net/projects/polyclipping/files/Older%20versions/clipper_ver4.10.0.zip) (but may take time to propagate around SF servers).

I've also just now uploaded clipper_ver5.1.6.zip but according to Marcus there's a problem with that package.

I've also encountered a preview sizing problem (but using the pre-compiled extension in Windows 10). The previiew window will on occasions maximize to the full screen with no way to...

> This adds the CLIPPER2_DLL to all classes and methods that are in the headers that have a cpp implementation. I'm wondering if exporting classes is the best approach for...

> Personally, I would prefer to keep the classes. All shared libraries in C++ bump into this in one form or another. I appreciate that exporting C++ classes may be...

Following up on my question [here](https://github.com/AngusJohnson/Clipper2/pull/245#issuecomment-1264602297)... I'm still not persuaded that exporting classes is better that exporting well designed functions. For example ISTM that the following function would provide all...

> As for defining wrappers - it would only increase code maintenance difficulty Well I'm certainly motivated to avoid code maintenance as much as possible. And part of that is...

> But Delphi surely can't import C++ classes? So for that use case, there should be a plain C API, right? And why I'm still (very slightly) leaning toward function...