From 3bb134969eb624e859a546fd7142fe2eae076346 Mon Sep 17 00:00:00 2001 From: wm4 Date: Tue, 30 Aug 2016 23:45:58 +0200 Subject: m_option: remove M_OPT_TYPE_DYNAMIC flag It's actually redundant with whether m_option_type.free is set. Some option types were flagged inconsistently. Its only use was for running an additional sanity check without any real functionality. --- options/m_option.h | 10 +--------- 1 file changed, 1 insertion(+), 9 deletions(-) (limited to 'options/m_option.h') diff --git a/options/m_option.h b/options/m_option.h index 80be447c42..847cd1097c 100644 --- a/options/m_option.h +++ b/options/m_option.h @@ -403,19 +403,11 @@ struct m_option { */ #define M_OPT_TYPE_ALLOW_WILDCARD (1 << 1) -// Dynamic data type. -/** This flag indicates that the data is dynamically allocated (m_option::p - * points to a pointer). It enables a little hack in the \ref Config which - * replaces the initial value of such variables with a dynamic copy in case - * the initial value is statically allocated (pretty common with strings). - */ -#define M_OPT_TYPE_DYNAMIC (1 << 2) - // The parameter is optional and by default no parameter is preferred. If // ambiguous syntax is used ("--opt value"), the command line parser will // assume that the argument takes no parameter. In config files, these // options can be used without "=" and value. -#define M_OPT_TYPE_OPTIONAL_PARAM (1 << 3) +#define M_OPT_TYPE_OPTIONAL_PARAM (1 << 2) ///////////////////////////// Parser flags ///////////////////////////////// -- cgit v1.2.3