Name |
Last commit
|
Last update |
---|---|---|
.. | ||
add.c | ||
backend.c | ||
config_helpers.c | ||
config_helpers.h | ||
configlevel.c | ||
global.c | ||
include.c | ||
multivar.c | ||
new.c | ||
read.c | ||
refresh.c | ||
rename.c | ||
snapshot.c | ||
stress.c | ||
validkeyname.c | ||
write.c |
In the check for multiline, we traverse the backslashes from the end backwards and int the end assert that we haven't gone past the beginning of the line. We make sure of this in the loop condition, but we also check in the return value. However, for certain configurations, a line in a multiline variable might be empty to aid formatting. In that case, 'end' == 'start', since we ended up looking at the first char which made it a multiline. There is no need for the (end > start) check in the return, since the loop guarantees we won't go further back than the first char in the line, and we do accept the first char to be the final backslash. This fixes #2483.
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
add.c | Loading commit data... | |
backend.c | Loading commit data... | |
config_helpers.c | Loading commit data... | |
config_helpers.h | Loading commit data... | |
configlevel.c | Loading commit data... | |
global.c | Loading commit data... | |
include.c | Loading commit data... | |
multivar.c | Loading commit data... | |
new.c | Loading commit data... | |
read.c | Loading commit data... | |
refresh.c | Loading commit data... | |
rename.c | Loading commit data... | |
snapshot.c | Loading commit data... | |
stress.c | Loading commit data... | |
validkeyname.c | Loading commit data... | |
write.c | Loading commit data... |