From: Richard Palethorpe <rpalethorpe@suse.de>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] lib: tst_bool_expr: Add support for strings
Date: Wed, 11 Nov 2020 14:19:00 +0000 [thread overview]
Message-ID: <87mtzoou23.fsf@suse.de> (raw)
In-Reply-To: <20201111131131.17360-1-chrubis@suse.cz>
Hello,
Cyril Hrubis <chrubis@suse.cz> writes:
> diff --git a/lib/tst_bool_expr.c b/lib/tst_bool_expr.c
> index dd147cde3..35ffa5a80 100644
> --- a/lib/tst_bool_expr.c
> +++ b/lib/tst_bool_expr.c
> @@ -64,6 +64,7 @@ static unsigned int tokenize(const char *expr, struct tst_expr_tok *last)
> {
> size_t i, j;
> unsigned int token_cnt = 0;
> + int in_string = 0;
>
> for (j = i = 0; expr[i]; i++) {
Why not skip the whole switch statement if in_string and just check for
the closing '"' instead?
> switch (expr[i]) {
> @@ -72,14 +73,21 @@ static unsigned int tokenize(const char *expr, struct tst_expr_tok *last)
> case '!':
> case '&':
> case '|':
> - token_cnt += new_tok(&last, &expr[j], i - j);
> - token_cnt += new_tok(&last, &expr[i], 1);
> - j = i+1;
> + if (!in_string) {
> + token_cnt += new_tok(&last, &expr[j], i - j);
> + token_cnt += new_tok(&last, &expr[i], 1);
> + j = i+1;
> + }
> break;
> case '\t':
> case ' ':
> - token_cnt += new_tok(&last, &expr[j], i - j);
> - j = i+1;
> + if (!in_string) {
> + token_cnt += new_tok(&last, &expr[j], i - j);
> + j = i+1;
> + }
> + break;
> + case '"':
> + in_string = !in_string;
> break;
> default:
> break;
> --
> 2.26.2
It should probably be an error if tokenize exits with in_string=1?
--
Thank you,
Richard.
next prev parent reply other threads:[~2020-11-11 14:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 13:11 [LTP] [PATCH] lib: tst_bool_expr: Add support for strings Cyril Hrubis
2020-11-11 14:19 ` Richard Palethorpe [this message]
2020-11-11 14:37 ` Cyril Hrubis
2020-11-11 17:38 ` Richard Palethorpe
2020-11-12 13:02 ` Cyril Hrubis
2020-11-12 14:02 ` Richard Palethorpe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mtzoou23.fsf@suse.de \
--to=rpalethorpe@suse.de \
--cc=ltp@lists.linux.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).