From: Denis KENZIOR <denis.kenzior@trolltech.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] [PATCH] XML SDP Record Registration
Date: Thu, 23 Nov 2006 10:51:17 +1000 [thread overview]
Message-ID: <200611231051.18032.denis.kenzior@trolltech.com> (raw)
In-Reply-To: <1164176698.23477.17.camel@localhost>
Marcel,
Oof, ouch.
In my defense, I followed the advice given in Linux CodingStyle document.
Most of the indentation issues you had a problem with was due to me using
'indent' with the suggested options.
In the future I will happily follow the code style conventions you outline.
However, given that this is my first serious submission I cannot be expected
to 'guess' the conventions if they are not written down, especially since
these are not outlined in the Linux CodingStyle document.
Since it seems that BlueZ has further conventions that developers should be
following, which are not outlined in the Linux Coding Style documents, I
suggest that you include them on the Coding Style section of the Development
page of bluez.org to avoid such problems in the future :)
Regards,
-Denis
> You are doing way too much casts. Especially all casts for malloc() and
> free() are totally unneeded. Make sure you include malloc.h and
> everything will be fine. Check the manual pages for needed includes if
> you are unsure. Every cast has a potential to hide an error. Please do
> only casts if you really have to and you are 100% sure it is the only
> way to make this code working.
>
> Pointer are never initialized with "= 0". Never. If you have to, then
> it is "= NULL". The same applies to any comparison and I prefer doing
> this with "!" as NULL check.
>
> In general, the assigned of a variable when declaring it will only hide
> programming mistakes that a compiler warning might have found. This
> applies to any compiler warning you see. Don't try to hide. Understand
> the real cause for it and fix that.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-11-23 0:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-21 5:04 [Bluez-devel] [PATCH] XML SDP Record Registration Denis KENZIOR
2006-11-21 7:41 ` Marcel Holtmann
2006-11-21 11:47 ` Marcel Holtmann
2006-11-21 23:59 ` Denis KENZIOR
2006-11-22 6:24 ` Marcel Holtmann
2006-11-23 0:51 ` Denis KENZIOR [this message]
2006-11-23 4:46 ` 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=200611231051.18032.denis.kenzior@trolltech.com \
--to=denis.kenzior@trolltech.com \
--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