Greetings, D aficionados.

I only regret that I did not discover your wonderful language sooner, as I probably would have written my entire library in D instead of using C++.

In the meantime, since I was already using SWIG, I have added bindings for the D language, so you can add untraceable digital cash, and other cool financial cryptography, to your D projects:

https://github.com/FellowTraveler/Open-Transactions/wiki

FellowTraveler Wrote:

> Greetings, D aficionados.
> 
> I only regret that I did not discover your wonderful language sooner, as I probably would have written my entire library in D instead of using C++.
> 
> In the meantime, since I was already using SWIG, I have added bindings for the D language, so you can add untraceable digital cash, and other cool financial cryptography, to your D projects:
> 
> https://github.com/FellowTraveler/Open-Transactions/wiki

Shouldn't lesser license require dynamic linking so that licensee can modify it and run proprietary code with the modified version? If linking is static, this is impossible.

Kagamin Wrote:

> FellowTraveler Wrote:
> 
> > Greetings, D aficionados.
> > 
> > I only regret that I did not discover your wonderful language sooner, as I probably would have written my entire library in D instead of using C++.
> > 
> > In the meantime, since I was already using SWIG, I have added bindings for the D language, so you can add untraceable digital cash, and other cool financial cryptography, to your D projects:
> > 
> > https://github.com/FellowTraveler/Open-Transactions/wiki
> 
> Shouldn't lesser license require dynamic linking so that licensee can modify it and run proprietary code with the modified version? If linking is static, this is impossible.


The OT-API resides in a shared library, (DLL.) So yes, it is dynamically linked to your own application.

A D wrapper is provided with the library for your convenience.

-FT