On Wednesday, May 5, 2021 at 1:45:55 AM UTC-5, Fred Killet wrote:
> Dear software developers,
>
> here I post a hint for people who develop programs with geodetic functionality like coordinate transformations, datum shifts or distance calculations. For this you can easily include ready for use geodetic functions from my Geodetic Development Kit GeoDLL. The Dynamic Link Library can be used with almost all modern programming languages like C, C++, C#, Basic, Delphi, Pascal, Java, Fortran, xSharp, MS-Office and so on. Examples and interfaces are available for many programming languages.
>
> GeoDLL is a professional Geodetic Development Kit or Geodetic Function Library for worldwide 2D and 3D coordinate transformations and datum shifts with highest accuracy. Also: Helmert and Molodensky parameters, NTv2, HARN, INSPIRE, EPSG, elevation model (DEM), distance and time zone calculation, meridian convergence and much more. GeoDLL is available as 32bit and 64bit DLL and as C / C++ source code.
>
> The DLL is very fast, secure and compact thanks to the consistent development in C / C++ with Microsoft Visual Studio. The geodetic functions are available in 32bit and 64bit architecture. All functions are prepared for multithreading and server operating.
>
> You find a free downloadable test version on https://www.killetsoft.de/p_gdla_e.htm
> Notes about the NTv2 support can be found here: https://www.killetsoft.de/t_ntv2_e.htm
> Report on the quality of the coordinate transformations: https://www.killetsoft.de/t_1705_e.htm
>
> Best regards and stay healthy!
> Fred
>
> Email: https://www.killetsoft.de/email.htm?lan=e&btr=News

Fred, you shouldn't be posting this to comp.lang.ada until you have actually designed & implemented an actual Ada binding to your library (or at least tried to do so, and need advice from Ada experts to complete the Ada binding). This likely goes for other languages as well, especially ones that have a culture, set of idioms, or philosophy/rationale that differs drastically from C and/or C++; indeed most non-C & non-C++ languages do have such drastic differences, hence why their programmers are not using C and/or C++. Yes, I understand that many languages (or specific compilers such as GNAT for Ada) have some degree of C-language importation capabilities. But quite often, as in GNAT's case, that importation (if it successfully completes at all) results in a thin binding that is either practically unworkable due to incompleteness or is intolerable in the culture, idioms, and/or philosophy/rationale of the imported-into programming language—hence the need for a human-designed thicker binding that is attuned to the culture, idioms, and philosophy/rationale. Portions of the Ada community would welcome a well-designed Ada thick binding to your library, but until you complete it or need advice from Ada experts in designing it, you should refrain from announcing nonAda variants of your library on comp.lang.ada.