aboutsummaryrefslogtreecommitdiffstats
path: root/src/libstrongswan/settings/settings.h
Commit message (Collapse)AuthorAgeFilesLines
* settings: Fix possible undefined behavior with va_start() and boolTobias Brunner2017-09-181-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes compilation with -Werror when using Clang 4.0 (but not 3.9) and possibly prevents undefined behavior. According to the C standard the following applies to the second parameter of the va_start() macro (subclause 7.16.1.4, paragraph 4): The parameter parmN is the identifier of the rightmost parameter in the variable parameter list in the function definition (the one just before the ...). If the parameter parmN is declared with the register storage class, with a function or array type, or with a type that is not compatible with the type that results after application of the default argument promotions, the behavior is undefined. Because bool is usually just 1 byte and therefore smaller than int (i.e. the result of default argument promotion) its use as last argument before ... might result in undefined behavior. This theoretically can also apply to enums as a compiler may use a smaller base type than int. Since Clang 3.9 (currently in use on Travis by default) a warning is issued about this, however, that version did not yet compare the actual size of the argument's type, causing warnings where they are not warranted (basically for all cases where enum types are used for the last argument). This was apparently fixed with Clang 4.0, which only warns about this use of bool with va_start(), which makes sense.
* Use standard unsigned integer typesAndreas Steffen2016-03-241-5/+5
|
* settings: Add settings_value_as_uint64() helper functionTobias Brunner2015-11-111-0/+9
|
* settings: Add methods and a constructor to parse settings from stringsTobias Brunner2015-07-281-0/+54
|
* settings: strongswan.conf must be loaded explicitlyTobias Brunner2014-05-151-1/+3
|
* settings: Move to a separate folderTobias Brunner2014-05-151-0/+351