linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] [DBUS-PATCH] cleanup
Date: Mon, 17 Oct 2005 11:35:12 +0200	[thread overview]
Message-ID: <1129541712.24835.59.camel@blade> (raw)
In-Reply-To: <e1effdeb0510140703t4080f782o8fcdef057fa00c06@mail.gmail.com>

Hi Claudio,

> Minor changes:
>  - removed some logs
>  - added verification for dbus_connection_list_registered function. It
> can return FALSE if there is no memory to allocate the child entries

the patch is now in the CVS. The whitespace thing is getting better and
I hope you use an editor that is visualizing them for you.

There are some programming styles in the code that we need to change,
because this code is getting ugly otherwise. Here is a bad example:

void func(void)
{
	if (test) {
		do_something();
	}
}

This will end up in nesting statements and you have to indent to deep to
keep it readable somehow. So the preferred way is:

void func(void)
{
	if (!test)
		return;

	do_something();
}

If a function is some lines longer this is not a big problem for the
understanding of the code, but if it is indented to deep then the code
becomes hard to read.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-10-17  9:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-14 14:03 [Bluez-devel] [DBUS-PATCH] cleanup Claudio Takahasi
2005-10-17  9:35 ` Marcel Holtmann [this message]
2005-10-20  9:07   ` Marcel Holtmann

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=1129541712.24835.59.camel@blade \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    /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).