Re: Version API

Elliot Saba writes: > The patch looks perfect. Thank you! Perfect or not, it's now pushed to the repository. Regards, /Niels -- Niels Möller. PGP-encrypted email is preferred. Keyid C0B98E26. Internet email is subject to wholesale government surveillance. _

Re: Version API

The patch looks perfect. Thank you! On Fri, May 1, 2015, 13:36 Niels Möller wrote: > Elliot Saba writes: > > > Right now, the way we're trying to solve this is by using dlsym() to look > > for functions that are included in one API version, and not another. > This > > isn't quite as easy as usi

Re: Version API

Elliot Saba writes: > Right now, the way we're trying to solve this is by using dlsym() to look > for functions that are included in one API version, and not another. This > isn't quite as easy as using a version number, but is what we will do to > tell the difference between, e.g. 2.7.1 and 3.0

Re: Version API

Hello there! Thank you for your quick response: Right now, the way we're trying to solve this is by using dlsym() to look for functions that are included in one API version, and not another. This isn't quite as easy as using a version number, but is what we will do to tell the difference between

Re: Version API

Elliot Saba writes: > I maintain the Julia language bindings for Nettle > which loads the dynamic library > and generates methods to use Nettle's cryptographic functions on the fly. Nice! > This process does not use header files, it's similar to Python

Version API

Hello there, I saw the recent addition of the version #define's, which are great, but a runtime function that I can call to find out libnettle's API is essential for dynamic bindings. I maintain the Julia language bindings for Nettle which loads the dynam