Open Source Telephony
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: ofono@ofono.org
Subject: Re: [PATCH 3/4] Add parser for file list objects
Date: Tue, 16 Mar 2010 11:44:24 -0700	[thread overview]
Message-ID: <1268765064.2700.25.camel@localhost.localdomain> (raw)
In-Reply-To: <1268733700-30154-3-git-send-email-yang.gu@intel.com>

[-- Attachment #1: Type: text/plain, Size: 1937 bytes --]

Hi Yang,

> ---
>  src/stkutil.c |   42 ++++++++++++++++++++++++++++++++++++++++++
>  src/stkutil.h |    6 ++++++
>  2 files changed, 48 insertions(+), 0 deletions(-)
> 
> diff --git a/src/stkutil.c b/src/stkutil.c
> index ceba2d5..9f3bc0b 100644
> --- a/src/stkutil.c
> +++ b/src/stkutil.c
> @@ -406,6 +406,46 @@ static gboolean parse_dataobj_tone(struct comprehension_tlv_iter *iter,
>  	return TRUE;
>  }
>  
> +/* Defined in TS 102.223 Section 8.18 */
> +static gboolean parse_dataobj_file_list(struct comprehension_tlv_iter *iter,
> +						void *user)
> +{
> +	GSList **fl = user;
> +	const unsigned char *data;
> +	unsigned int len;
> +	unsigned int i;
> +	unsigned int start = 1;
> +	struct stk_file *sf;
> +
> +	if (comprehension_tlv_iter_get_tag(iter) !=
> +			STK_DATA_OBJECT_TYPE_FILE_LIST)
> +		return FALSE;
> +
> +	len = comprehension_tlv_iter_get_length(iter);
> +	if (len < 5)
> +		return FALSE;
> +
> +	data = comprehension_tlv_iter_get_data(iter);
> +
> +	if (data[start] != 0x3f)
> +		return FALSE;
> +
> +	for (i = start + 4; i <= len; i += 2) {
> +		if ((data[i] == 0x3f) || (i == len)) {
> +			sf = g_new0(struct stk_file, 1);
> +			sf->file = g_malloc(i-start);
> +			memcpy(sf->file, data+start, i-start);
> +			sf->len = i - start;
> +			*fl = g_slist_prepend(*fl, sf);
> +			start = i;
> +		}

doing a simple continue statement is way better.

	if (data[i] != 0x3f && i != len)
		continue;

Also there are not extra braces needed around expression in an if
statement. And i-start would have to be i - start.

When using g_new0 and g_malloc you result in exit on OOM. We try to
avoid that whenever possible. So I prefer using g_try_new0 and
g_try_malloc except there is a reason to just accept exit on OOM.

Personally the whole counting looks pretty complicated. I think it needs
either some documentation or made simpler.

Regards

Marcel



  parent reply	other threads:[~2010-03-16 18:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-16 10:01 [PATCH 1/4] Fix the structure of stk_subaddress Yang Gu
2010-03-16 10:01 ` [PATCH 2/4] Handle the conversion failure when parsing item Yang Gu
2010-03-16 10:01   ` [PATCH 3/4] Add parser for file list objects Yang Gu
2010-03-16 10:01     ` [PATCH 4/4] Add parser for location information objects Yang Gu
2010-03-16 18:46       ` Marcel Holtmann
2010-03-16 18:44     ` Marcel Holtmann [this message]
2010-03-16 20:01     ` [PATCH 3/4] Add parser for file list objects Denis Kenzior
2010-03-16 18:36   ` [PATCH 2/4] Handle the conversion failure when parsing item Marcel Holtmann
2010-03-16 20:27     ` Denis Kenzior
2010-03-17  4:40       ` Marcel Holtmann
2010-03-16 20:29   ` Denis Kenzior
2010-03-17  3:33     ` Gu, Yang
2010-03-17  4:44       ` Marcel Holtmann
2010-03-16 20:28 ` [PATCH 1/4] Fix the structure of stk_subaddress 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=1268765064.2700.25.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --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