From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 03/11] Add basic command parsing
Date: Wed, 17 Mar 2010 12:02:17 -0600 [thread overview]
Message-ID: <201003171302.17451.denkenz@gmail.com> (raw)
In-Reply-To: <1268836241-4834-3-git-send-email-zhenhua.zhang@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1847 bytes --]
Hi Zhenhua,
> According to V.250 5.3.1, the basic command is either a single
> character or the '&' followed by a single character.
> ---
> gatchat/gatserver.c | 68
> ++++++++++++++++++++++++++++++++++++++++++++++++++- 1 files changed,
67
> insertions(+), 1 deletions(-)
>
> diff --git a/gatchat/gatserver.c b/gatchat/gatserver.c
> index fb82ad4..b68894d 100644
> --- a/gatchat/gatserver.c
> +++ b/gatchat/gatserver.c
> @@ -211,10 +211,67 @@ static char *parse_extended_command(GAtServer
> *server, const char *buf, return NULL;
> }
>
> +static gboolean get_basic_prefix(const char *buf, char *prefix)
> +{
> + char c = *buf;
> +
> + if (g_ascii_isalpha(c)) {
if (!g_ascii_isalpha && c != '&')
return
No nested ifs if you can avoid them please.
> + c = g_ascii_toupper(c);
> + if (c == 'S') {
> + int i = 0;
> +
> + prefix[0] = 'S';
> +
> + /* V.250 5.3.2 'S' command follows with
> + * a parameter number.
> + */
> + while (g_ascii_isdigit(buf[++i]))
> + prefix[i] = buf[i];
> +
> + prefix[i] = '\0';
> + } else {
> + prefix[0] = c;
> + prefix[1] = '\0';
> + }
> + } else if (c == '&') {
> + prefix[0] = '&';
> + prefix[1] = g_ascii_toupper(buf[1]);
> + prefix[2] = '\0';
> + } else
> + return FALSE;
> +
> + return TRUE;
> +}
> +
> static char *parse_next_command(GAtServer *server, const char *buf,
> @@ -263,6 +320,15 @@ static void server_parse_line(GAtServer *server, char
> *line) break;
> }
>
> + /* Commands like ATA, ATD, ATZ cause the remainder line
> + * to be ignored.
> + */
> + if (!strcmp(prefix, "A") || !strcmp(prefix, "D") ||
> + !strcmp(prefix, "Z")) {
> + g_free(command);
> + break;
> + }
> +
strcmp might be overkill here
> buf += strlen(command);
>
> g_free(command);
>
next prev parent reply other threads:[~2010-03-17 18:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 14:30 [PATCH 01/11] Rename g_at_server_send_result Zhenhua Zhang
2010-03-17 14:30 ` [PATCH 02/11] Add framework of server parser Zhenhua Zhang
2010-03-17 14:30 ` [PATCH 03/11] Add basic command parsing Zhenhua Zhang
2010-03-17 14:30 ` [PATCH 04/11] Add extended " Zhenhua Zhang
2010-03-17 14:30 ` [PATCH 05/11] Add server at command data structure Zhenhua Zhang
2010-03-17 14:30 ` [PATCH 06/11] Add notify at command callback Zhenhua Zhang
2010-03-17 14:30 ` [PATCH 07/11] Add g_at_server_register and unregister callback Zhenhua Zhang
2010-03-17 14:30 ` [PATCH 08/11] Add G_AT_SERVER_RESULT_EXT_ERROR Zhenhua Zhang
2010-03-17 14:30 ` [PATCH 09/11] Fix do not emit error if extended error has emitted Zhenhua Zhang
2010-03-17 14:30 ` [PATCH 10/11] Refactor g_at_server_send_final Zhenhua Zhang
2010-03-17 14:30 ` [PATCH 11/11] Add utilities to send server response Zhenhua Zhang
2010-03-17 18:23 ` [PATCH 06/11] Add notify at command callback Denis Kenzior
2010-03-17 18:02 ` Denis Kenzior [this message]
2010-03-17 17:55 ` [PATCH 02/11] Add framework of server parser Denis Kenzior
2010-03-17 14:38 ` [PATCH 01/11] Rename g_at_server_send_result Zhenhua Zhang
2010-03-17 18:24 ` Denis Kenzior
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=201003171302.17451.denkenz@gmail.com \
--to=denkenz@gmail.com \
--cc=ofono@ofono.org \
/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