| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
| |
Since 4b670a20 we require an explicit strongswan.conf to re-load configurations.
However, the define was missing in the build, breaking SIGHUP based config
reloading.
Fixes #651.
|
| |
|
|
|
|
|
|
|
| |
As the behavior was inconsistent for empty strings or strings with characters
appended to a number, testing the code failed on some platforms. The new rules
are more strict, returning the default if additional characters or an empty
string was found for a setting.
|
|
|
|
|
|
| |
Found due to %option nodefault. A match for } was actually missing
and # was not properly matched if it was part of an include statement
on the last line of a file that did not end with a newline.
|
|
|
|
|
| |
This was useful during development, but we accept that matching \n together
with %option yylineno impacts performance.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
With Bison 3.x support for YYLEX_PARAM has been removed and %lex-param
should be used. Unfortunately, that option does not take expressions.
Instead we use a wrapper function that calls the lexer with the proper
scanner object, which should also be backward compatible to older Bison
versions.
|
|
|
|
|
| |
Newer Bison versions declare the parser function in the header, which
requires custom types.
|
|
|
|
| |
Basically reintroducing 2a38b4556e9fd8102bd6c6c61f2893599a5e8e51.
|
| |
|
|
|
|
|
| |
Instead of removing and caching all values of a previous config, we only
do this for actually removed sections/settings.
|
| |
|
|
|
|
|
|
|
| |
This is not thread safe. If threads are reading from pointers to existing
values they could get a partially updated invalid value.
Refactored assignment to a separate function.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This parser features several improvements over the existing one.
For instance, quoted strings (with escape sequences), unlimited includes,
relaxed newline handling (e.g. at the end of files or before/after { and }),
and the difference between empty and unset values (key = vs. key = "").
It also complains a lot more about invalid syntax. The current one accepts
pretty odd stuff (like settings or sections without name) without any
errors or warnings.
|
|
|
|
| |
This allows us to use them in the upcoming parser.
|
| |
|
|
|