> Instead of that we have some support for it in FreeBSD
My google fu is failing me right now but FreeBSD also has a shared library used for reading/parsing config files and providing either a common or universal dsl for all conf files using the same library. This is one of the benefits of using an OS instead of a distribution - all the tools are developed holistically and refactors such as providing a shared, universal input or output format, sandboxing everything with capsicum, etc across the board are much more possible.
EDIT
Remembered it. Surprised at how bad Google was at finding this, though!
UCL - Universal Configuration Language [0]. Introduced in a paper by Allan Jude in 2015 [1]. Man page: libucl(3) [2].
I did read the article, but "BSD layer synchronized with FreeBSD 5" somewhat late in the project didn't itself give me the impression it was derived from work in FreeBSD. That said, I appreciate the poke to go do some more work :)
Interesting, I would think it would be easier to use LibreSSL for this since the OpenBSD folks are so conservative that the modern APIs are likely to be stable. Maybe they want to use more of the legacy APIs that the OpenBSD folks are excising?
if you look through their drivers, they use a sort of c++ without exceptions, but last i remember from debugging network drivers on osx, they looked like they were forked from freebsd a fairly long time ago, but were for a long time close enough to be able to see the roots(i don't know if it's still like that)
Yes; this was good to ''cut my teeth on'', as it's a rather simple package and, being so self-contained, I'm actually entirely pleased with its specification.
>In base, OpenBSD only supports C/C++, however a Perl interface is also included.
I'm soon going to drop by the OpenBSD mailing list and see if they're interested in including this in their prepackaged GNAT. It won't harm to ask.
Related to this, I intend to write a binding for Common Lisp, at some point, although that will be far more arduous, all things considered.
reply