An ini file is segmented into Sections, declared by the following syntax:
[Section Name]
i.e. the section name enclosed in square brackets, alone on a line. Sections names are allowed to contain any character but square brackets or linefeeds. Slashes (/) are also reserved for hierarchical sections (see below).
In any section are zero or more variables, declared with the following syntax:
Key = value ; comment
The key is any string (possibly containing blanks). The value is any character on the right side of the equal sign. Values can be given enclosed with quotes. If no quotes are present, the value is understood as containing all characters between the first and the last non-blank characters. The following declarations are identical:
Hello = "this is a long string value" ; comment
Hello = this is a long string value ; comment
The semicolon and comment at the end of the line are optional. If there is a comment, it starts from the first character after the semicolon up to the end of the line.
Comments in an ini file are:
ar program on your machine to build a library (.a) from a set of object (.o) files.Defaults are set for the gcc compiler and the standard ar library builder.
Type 'make', that should do it.
To use the library in your programs, add the following line on top of your module:
#include "iniparser.h"
And link your program with the iniparser library by adding -liniparser.a to the compile line.
See the file test/initest.c for an example.
[Section]
Keyword = value ; comment
is converted to the following key pair:
("section:keyword", "value")
This means that if you want to retrieve the value that was stored in the section called Pizza, in the keyword Cheese, you would make a request to the dictionary for "pizza:cheese". All section and keyword names are converted to lowercase before storage in the structure. The value side is conserved as it has been parsed, though.
Section names are also stored in the structure. They are stored using as key the section name, and a NULL associated value. They can be queried through iniparser_find_entry().
To launch the parser, simply use the function called iniparser_load(), which takes an input file name and returns a newly allocated dictionary structure. This latter object should remain opaque to the user and only accessed through the following accessor functions:
Finally, discard this structure using iniparser_freedict().
All values parsed from the ini file are stored as strings. The getint, getdouble and getboolean accessors are just converting these strings to the requested type on the fly, but you could basically perform this conversion by yourself after having called the getstr accessor.
Notice that the iniparser_getboolean() function will return an integer (0 or 1), trying to make sense of what was found in the file. Strings starting with "y", "Y", "t", "T" or "1" are considered true values (return 1), strings starting with "n", "N", "f", "F", "0" are considered false (return 0). This allows flexible handling of boolean answers.
If you want to add extra information into the structure that was not present in the ini file, you can use iniparser_setstr() to insert a string.
A section depends on another section if it contains its name as a prefix, separated by slashes (/). For example: we have 2 main sections in the ini file. The first one is called Pizza and has two child subsections called Cheese and Ham. The second main section in the ini file is called Wine and has two child subsections called Year and Grape. As a tree, this could appear as:
|
+-- Pizza
| +-- Cheese
| +-- Ham
+-- Wine
+--- Year
+--- Grape
In an ini file, that would be converted to:
[Pizza]
[Pizza/Cheese]
Name = Gorgonzola ;
Origin = Italy ;
[Pizza/Ham]
Name = Parma ;
Origin = Italy ;
[Wine]
[Wine/Year]
Value = 1998 ;
[Wine/Grape]
Name = Cabernet Sauvignon ;
Origin = Chile ;
This proposal is actually more related to the way people write ini files, more than the parser presented here. But it is certainly a useful way of making tree-like data declarations without going through painful formats like XML.
Accessing the above tree would give something like (error checking removed for clarity sake):
dictionary * d ;
d = iniparser_load("example.ini");
printf("cheese name is %s\n", iniparser_getstr(d, "pizza/cheese:name"));
printf("grape name is %s\n", iniparser_getstr(d, "wine/grape:name"));
iniparser_freedict(d);
The whole ini file above is represented in the dictionary as the following list of pairs:
key value
"pizza" NULL
"pizza/cheese" NULL
"pizza/cheese:name" "Gorgonzola"
"pizza/cheese:origin" "Italy"
"pizza/ham" NULL
"pizza/ham:name" "Parma"
"pizza/ham:origin" "Italy"
"wine" NULL
"wine/year" NULL
"wine/year:value" "1998"
"wine/grape" NULL
"wine/grape:name" "Cabernet Sauvignon"
"wine/grape:origin" "Chile"