LIBUCL
Table of Contents generated with DocToc
- Introduction
- Basic structure
- Improvements to the json notation
- General improvements
- Emitter
- Validation
- Performance
- Conclusion
Introduction
This document describes the main features and principles of the configuration language called UCL - universal configuration language.
If you are looking for the libucl API documentation you can find it at this page.
Basic structure
UCL is heavily infused by nginx configuration as the example of a convenient configuration system. However, UCL is fully compatible with JSON format and is able to parse json files. For example, you can write the same configuration in the following ways:
- in nginx like:
param = value;
section {
param = value;
param1 = value1;
flag = true;
number = 10k;
time = 0.2s;
string = "something";
subsection {
host = {
host = "hostname";
port = 900;
}
host = {
host = "hostname";
port = 901;
}
}
}
- or in JSON:
{
"param": "value",
"section": {
"param": "value",
"param1": "value1",
"flag": true,
"number": 10000,
"time": "0.2s",
"string": "something",
"subsection": {
"host": [
{
"host": "hostname",
"port": 900
},
{
"host": "hostname",
"port": 901
}
]
}
}
}
Improvements to the json notation.
There are various things that make ucl configuration more convenient for editing than strict json:
General syntax sugar
- Braces are not necessary to enclose a top object: it is automatically treated as an object:
"key": "value"
is equal to:
{"key": "value"}
- There is no requirement of quotes for strings and keys, moreover,
:may be replaced=or even be skipped for objects:
key = value;
section {
key = value;
}
is equal to:
{
"key": "value",
"section": {
"key": "value"
}
}
- No commas mess: you can safely place a comma or semicolon for the last element in an array or an object:
{
"key1": "value",
"key2": "value",
}
Automatic arrays creation
- Non-unique keys in an object are allowed and are automatically converted to the arrays internally:
{
"key": "value1",
"key": "value2"
}
is converted to:
{
"key": ["value1", "value2"]
}
Named keys hierarchy
UCL accepts named keys and organize them into objects hierarchy internally. Here is an example of this process:
section "blah" {
key = value;
}
section foo {
key = value;
}
is converted to the following object:
section {
blah {
key = value;
}
foo {
key = value;
}
}
Plain definitions may be more complex and contain more than a single level of nested objects:
section "blah" "foo" {
key = value;
}
is presented as:
section {
blah {
foo {
key = value;
}
}
}
Convenient numbers and booleans
- Numbers can have suffixes to specify standard multipliers:
[kKmMgG]- standard 10 base multipliers (so1kis translated to 1000)[kKmMgG]b- 2 power multipliers (so1kbis translated to 1024)[s|min|d|w|y]- time multipliers, all time values are translated to float number of seconds, for example10minis translated to 600.0 and10msis translated to 0.01
- Hexadecimal integers can be used by
0xprefix, for examplekey = 0xff. However, floating point values can use decimal base only. - Booleans can be specified as
trueoryesoronandfalseornooroff. - It is still possible to treat numbers and booleans as strings by enclosing them in double quotes.
General improvements
Comments
UCL supports different style of comments:
- single line:
# - multiline:
/* ... */
Multiline comments may be nested:
# Sample single line comment
/*
some comment
/* nested comment */
end of comment
*/
Macros support
UCL supports external macros both multiline and single line ones:
.macro_name "sometext";
.macro_name {
Some long text
....
};
Moreover, each macro can accept an optional list of arguments in braces. These arguments themselves are the UCL object that is parsed and passed to a macro as options:
.macro_name(param=value) "something";
.macro_name(param={key=value}) "something";
.macro_name(.include "params.conf") "something";
.macro_name(#this is multiline macro
param = [value1, value2]) "something";
.macro_name(key="()") "something";
UCL also provide a convenient include macro to load content from another files to the current UCL object. This macro accepts either path to file:
.include "/full/path.conf"
.include "./relative/path.conf"
.include "${CURDIR}/path.conf"
or URL (if ucl is built with url support provided by either libcurl or libfetch):
.include "http://example.com/file.conf"
.include macro supports a set of options:
try(default: false) - if this option istruethan UCL treats errors on loading of this file as non-fatal. For example, such a file can be absent but it won't stop the parsing of the top-level document.sign(default: false) - if this option istrueUCL loads and checks the signature for a file from path named<FILEPATH>.sig. Trusted public keys should be provided for UCL API after parser is created but before any configurations are parsed.glob(default: false) - if this option istrueUCL treats the filename as GLOB pattern and load all files that matches the specified pattern (normally the format of patterns is defined inglobmanual page for your operating system). This option is meaningless for URL includes.url(default: true) - allow URL includes.path(default: empty) - A UCL_ARRAY of directories to search for the include file. Search ends after the first match, unlessglobis true, then all matches are included.prefix(default false) - Put included contents inside an object, instead of loading them into the root. If nokeyis provided, one is automatically generated based on each files basename()key(default: ) - Key to load contents of include into. If the key already exists, it must be the correct typetarget(default: object) - Specify if theprefixkeyshould be an object or an array.priority(default: 0) - specify priority for the include (see below).duplicate(default: 'append') - specify policy of duplicates resolving:append- default strategy, if we have new object of higher priority then it replaces old one, if we have new object with less priority it is ignored completely, and if we have two duplicate objects with the same priority then we have a multi-value key (implicit array)merge- if we have object or array, then new keys are merged inside, if we have a plain object then an implicit array is formed (regardless of priorities)error- create error on duplicate keys and stop parsingrewrite- always rewrite an old value with new one (ignoring priorities)
Priorities are used by UCL parser to manage the policy of objects rewriting during including other files as following:
- If we have two objects with the same priority then we form an implicit array
- If a new object has bigger priority then we overwrite an old one
- If a new object has lower priority then we ignore it
By default, the priority of top-level object is set to zero (lowest priority). Currently, you can define up to 16 priorities (from 0 to 15). Includes with bigger priorities will rewrite keys from the objects with lower priorities as specified by the policy. The priority of the top-level or any other object can be changed with the .priority macro, which has no options and takes the new priority:
# Default priority: 0.
foo = 6
.priority 5
# The following will have priority 5.
bar = 6
baz = 7
# The following will be included with a priority of 3, 5, and 6 respectively.
.include(priority=3) "path.conf"
.include(priority=5) "equivalent-path.conf"
.include(priority=6) "highpriority-path.conf"
Variables support
UCL supports variables in input. Variables are registered by a user of the UCL parser and can be presented in the following forms:
${VARIABLE}$VARIABLE
UCL currently does not support nested variables. To escape variables one could use double dollar signs:
$${VARIABLE}is converted to${VARIABLE}$$VARIABLEis converted to$VARIABLE
However, if no valid variables are found in a string, no expansion will be performed (and $$ thus remains unchanged). This may be a subject to change in future libucl releases.
Multiline strings
UCL can handle multiline strings as well as single line ones. It uses shell/perl like notation for such objects:
key = <<EOD
some text
splitted to
lines
EOD
In this example key will be interpreted as the following string: some text\nsplitted to\nlines. Here are some rules for this syntax:
- Multiline terminator must start just after
<<symbols and it must consist of capital letters only (e.g.<<eofor<< EOFwon't work); - Terminator must end with a single newline character (and no spaces are allowed between terminator and newline character);
- To finish multiline string you need to include a terminator string just after newline and followed by a newline (no spaces or other characters are allowed as well);
- The initial and the final newlines are not inserted to the resulting string, but you can still specify newlines at the beginning and at the end of a value, for example:
key <<EOD
some
text
EOD
Single quoted strings
It is possible to use single quoted strings to simplify escaping rules. All values passed in single quoted strings are NOT escaped, with two exceptions: a single ' character just before \ character, and a newline character just after \ character that is ignored.
key = 'value'; # Read as value
key = 'value\n\'; # Read as value\n\
key = 'value\''; # Read as value'
key = 'value\
bla'; # Read as valuebla
Emitter
Each UCL object can be serialized to one of the four supported formats:
JSON- canonic json notation (with spaces indented structure);Compacted JSON- compact json notation (without spaces or newlines);Configuration- nginx like notation;YAML- yaml inlined notation;messagepack- MessagePack binary format.
Validation
UCL allows validation of objects. It uses the same schema that is used for json: json schema v4. UCL supports the full set of json schema with the exception of remote references. This feature is unlikely useful for configuration objects. Of course, a schema definition can be in UCL format instead of JSON that simplifies schemas writing. Moreover, since UCL supports multiple values for keys in an object it is possible to specify generic integer constraints maxValues and minValues to define the limits of values count in a single key. UCL currently is not absolutely strict about validation schemas themselves, therefore UCL users should supply valid schemas (as it is defined in json-schema draft v4) to ensure that the input objects are validated properly.
Performance
Are UCL parser and emitter fast enough? Well, there are some numbers. I got a 19Mb file that consist of ~700 thousand lines of json (obtained via http://www.json-generator.com/). Then I checked jansson library that performs json parsing and emitting and compared it with UCL. Here are results:
jansson: parsed json in 1.3899 seconds
jansson: emitted object in 0.2609 seconds
ucl: parsed input in 0.6649 seconds
ucl: emitted config in 0.2423 seconds
ucl: emitted json in 0.2329 seconds
ucl: emitted compact json in 0.1811 seconds
ucl: emitted yaml in 0.2489 seconds
So far, UCL seems to be significantly faster than jansson on parsing and slightly faster on emitting. Moreover, UCL compiled with optimizations (-O3) performs significantly faster:
ucl: parsed input in 0.3002 seconds
ucl: emitted config in 0.1174 seconds
ucl: emitted json in 0.1174 seconds
ucl: emitted compact json in 0.0991 seconds
ucl: emitted yaml in 0.1354 seconds
You can do your own benchmarks by running make check in libucl top directory.
Conclusion
UCL has clear design that should be very convenient for reading and writing. At the same time it is compatible with JSON language and therefore can be used as a simple JSON parser. Macro logic provides an ability to extend configuration language (for example by including some lua code) and comments allow to disable or enable the parts of a configuration quickly.
![[DISCUSSION]: Using dot-notation for setting values](https://avatars.githubusercontent.com/u/101281?v=4)
5 Jul 19, 2022
19 Jan 5, 2022
2 Jun 10, 2022
72 Dec 11, 2022
1.1k Dec 28, 2022
28 Mar 1, 2024
7.6k Jan 7, 2023
25 Nov 2, 2020
1.2k Dec 30, 2022
228 Oct 31, 2022
2.4k Jan 7, 2023
3.5k Jan 8, 2023
138 Nov 25, 2022
67 Nov 16, 2022
18 Apr 19, 2021
49 Dec 11, 2022
5 Feb 28, 2022
16 Dec 5, 2022
27 Aug 3, 2022