-
Notifications
You must be signed in to change notification settings - Fork 6
Open
Description
When a parsing error is introduced in a DOTCONF_CB function by returning a non-NULL charptr, dotconf_command_loop() is supposed to return 0 indicating failure to parse. This works fine for the main configuration file, but not if errors are found in included configuration files. I will attach a test case shortly, where the following configuration file fails as expected:
# error.conf
Error 1
The following file succeeds as expected:
# ok.conf
Error 0
And the following file succeeds unexpectedly, while it does invoke the error handler:
# include_error.conf
Include "error.conf"
Metadata
Metadata
Assignees
Labels
No labels