Commit f5451582 authored by Masahiro Yamada's avatar Masahiro Yamada
Browse files

kconfig: stop supporting '.' and '/' in unquoted words



In my understanding, special characters such as '.' and '/' are
supported in unquoted words to use bare file paths in the "source"
statement.

With the previous commit surrounding all file paths with double
quotes, we can drop this.

Signed-off-by: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
parent 8636a1f9
Loading
Loading
Loading
Loading
+1 −2
Original line number Diff line number Diff line
@@ -555,8 +555,7 @@ char *expand_string(const char *in)

static bool is_end_of_token(char c)
{
	/* Why are '.' and '/' valid characters for symbols? */
	return !(isalnum(c) || c == '_' || c == '-' || c == '.' || c == '/');
	return !(isalnum(c) || c == '_' || c == '-');
}

/*
+2 −2
Original line number Diff line number Diff line
@@ -160,7 +160,7 @@ n [A-Za-z0-9_-]
		BEGIN(STRING);
	}
	\n	BEGIN(INITIAL); return T_EOL;
	({n}|[/.])+	{
	{n}+	{
		const struct kconf_id *id = kconf_id_lookup(yytext, yyleng);
		if (id && id->flags & TF_PARAM) {
			yylval.id = id;
@@ -170,7 +170,7 @@ n [A-Za-z0-9_-]
		yylval.string = text;
		return T_WORD;
	}
	({n}|[/.$])+	{
	({n}|$)+	{
		/* this token includes at least one '$' */
		yylval.string = expand_token(yytext, yyleng);
		if (strlen(yylval.string))