core: usually our enum's _INVALID and _MAX special values are named after the full type
In most cases we followed the rule that the special _INVALID and _MAX values we use in our enums use the full type name as prefix (in contrast to regular values that we often make shorter), do so for ExecDirectoryType as well. No functional changes, just a little bit of renaming to make this code more like the rest.
This commit is contained in:
+3
-3
@@ -128,8 +128,8 @@ typedef enum ExecDirectoryType {
|
||||
EXEC_DIRECTORY_CACHE,
|
||||
EXEC_DIRECTORY_LOGS,
|
||||
EXEC_DIRECTORY_CONFIGURATION,
|
||||
_EXEC_DIRECTORY_MAX,
|
||||
_EXEC_DIRECTORY_INVALID = -1,
|
||||
_EXEC_DIRECTORY_TYPE_MAX,
|
||||
_EXEC_DIRECTORY_TYPE_INVALID = -1,
|
||||
} ExecDirectoryType;
|
||||
|
||||
typedef struct ExecDirectory {
|
||||
@@ -251,7 +251,7 @@ struct ExecContext {
|
||||
bool address_families_whitelist:1;
|
||||
|
||||
ExecPreserveMode runtime_directory_preserve_mode;
|
||||
ExecDirectory directories[_EXEC_DIRECTORY_MAX];
|
||||
ExecDirectory directories[_EXEC_DIRECTORY_TYPE_MAX];
|
||||
|
||||
bool memory_deny_write_execute;
|
||||
bool restrict_realtime;
|
||||
|
||||
Reference in New Issue
Block a user