Structures | All structures used in the interface should be treated as internal opaque objects |
Types of configutration file encodings | Constants that define how configuration file is encoded |
Error tolerance constants | Constants in this section define what to do if error or warning encountered while parsing the INI file |
Parsing errors and warnings | Parsing errors and warnings |
Constants that define what meta data to collect | Constants in this section define what meta data to collect |
Access control check flags | |
▼Flags that define collision resolution logic. | |
Colliding values come from one section | Flags that define collision resolution logic for values in the same section. These flags should be used during parsing to handle duplicate keys in the same section of the ini file |
Colliding values come from two sections | Flags that define collision resolution logic between two values that come from two sections with the same name. These flags should be used during parsing to handle duplicate keys coming from the same section scattered across the ini file. These flags also can be used to specify the rules of merging values that come from two different configuration files |
Collision in two sections | Flags that define collision resolution logic between two sections. These flags should be used during parsing to handle duplicate sections scattered across the ini file. These flags also can be used to specify the rules of merging sections that come from two different configuration files |
Flags that define parsing rules | Flags that define how the file should be parsed |
Constants that define how to look for a value | Configuration file can allow several keys with the same name in one section. Use the constants below to define which value you are looking for. You can search for the next value only if you are looking for the same section and key as in the previous search. If you specify INI_GET_NEXT_VALUE but the section or key is different from the values that were used in the previous search the value will be ignored and the function will act as if INI_GET_FIRST_VALUE is specified. This functionality allows creating an attribute list and actually fetching every value including duplicate values in a single loop |
Constants and structures related to augmentation. | |
Core interface functions | Functions in this section allow manipulation with the configuration file, parsing data from the configuration file and storing it in a configuration object, merging configuration objects and other operations |
Section and attribute management | Functions in this section allow getting the lists of sections in the configuration file and keys in a section as arrays of strings |
Value management | This section contains value management functions. These functions can be used to interpret values that are stored in the configuration object in memory |
Flags used in add_xxx_value functions | These flags control the behavior of the add_xxx_value functions. Use these flags to specify how you want to process the key. Do you want the function to replace an existing key? Or may be you want to generate an error when function sees that there is a duplicate key? Or may be you do not want to check anything and just add the key to the section? |
API to create and modify configuration objects | Functions in this section allow creation, modification and deletion of sections and keys |