[Portland] gconf kconfig and uniconf

[Hubert Figuiere]

Jon Phillips wrote:
> Looks like uniconf is not moving much and there are only a couple of
> comments on it.

I can't really speak for them, but it is of my understanding that
wvstreams, the library that contains UniConf, is not really being
actively developed as an open source product anymore. The existing
public version is maintained by former NITI employees, but I suspect it
might become dormant...

UniConf has several design choices that makes it a problem to implement.
The biggest is that, for historical reasons, libwvstreams comes with its
own set of classes that duplicate what the Standard C++ library
provides. That alone is IMHO a big issue. Porting it to the Standard C++
library would be a major overall.
The second biggest is its reliance on a C++ API, but that can be worked
around if needed as it is somewhat designed to be bound to other languages.


Hub