Contents |
libelektra is written in C. It is very active and maintained and developed by the core developers.
The c-binding enhance the minimal API with a lot of useful functions for working with key, keysets and the key database. They include working with names, strings and useful shortcuts to achieve more comfortable working. This part is in unstable but has a test environment.
Status: Maintained by Markus
C++ allow powerful features like templates, exceptions and has a build in string class.
An exception hierachy will allow the safe use of elektra without checking return values all the time.
Templates allow using all datatypes you wish to get and set (just support Streams for your datatype) typesafe!
This binding is very new but has a test environment. It is actively developed, ideas and help is welcome!
Status: Is maintained by patrick
The python binding is very new and there are example programs. It is actively developed.
A binding using classes is in work.
There is no Testing Framework available for it.
Status: Is maintained by rotty
The scheme binding is very new and there are example programs. It is actively developed.
There is no Testing Framework available for it.
Status: Search for Maintainer
There is actually no Java binding available. But JRegistry uses elektra within Java, so its possible to extract a binding from there.
The Module is not tested. It is not known to work with the kdb* Functions.
Status: Search for Maintainer
There is a very outdated Ruby Binding which needs lots of work.
It uses the registry* functions. It is not known to work with kdb* and it is not tested. There is no Testing Framework available for it.
Status: Search for Maintainer
There is a outdated Lua Binding.
There is no Testing Framework available for it.
Status: Maintainer to begin needed!
There is no Perl cpan-module available now.
There is no Testing Framework available for it.
Status: Will be Maintained by seasonfive
There is no PHP Binding available now.
There is no Testing Framework available for it.
If your Binding has the status Search for Maintainer, change it here. But then please port to the kdb* API. But consider we will remove some (many) Functions to make the API thinner. But this will not take place before 1.0.