Please review the attached patch to add links to the flags for some functions in ini_configobj.h I am unclear as to what flags are allowed for the merge_flags parameter of ini_config_augment().
Hi,
I briefly looked at the patch and it looks good. Will you create pull request?
As for what flags can be used in ini_config_augment, here is the explanation from the header file
328 /** 329 * @defgroup mergesec Collision in two sections 330 * 331 * Flags that define collision resolution logic between two sections. 332 * These flags should be used during parsing to handle duplicate 333 * sections scattered across the ini file. 334 * These flags also can be used to specify the rules of merging 335 * sections that come from two different configuration files. 336 * 337 * @{ 338 */ 339 /** @brief Sections are merged */ 340 #define INI_MS_MERGE 0x0000 341 /** @brief Collision causes error */ 342 #define INI_MS_ERROR 0x0100 343 /** @brief First section is discarded */ 344 #define INI_MS_OVERWRITE 0x0200 345 /** @brief Second section is discarded */ 346 #define INI_MS_PRESERVE 0x0300 347 /** @brief Log errors if duplicate sections are detected; non-exclusive */ 348 /** This defaults to MERGE, but can be used with OVERWRITE and PRESERVE **/ 349 #define INI_MS_DETECT 0x0400
Metadata Update from @mzidek: - Custom field component adjusted to None - Custom field selected adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None
Feel free to ask if something is unclear :)
OK thanks for the clarification on the merge_flags parameter of ini_config_augment(). I submitted #3187
Fixed in master: 1b88dfb32b71502e9b4616586cd525886a391236
Metadata Update from @mzidek: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)