From: Stefano Garzarella <sgarzare@redhat.com>
To: Wei Yang <richardw.yang@linux.intel.com>
Cc: qemu-devel@nongnu.org, qemu-trivial@nongnu.org,
peter.maydell@linaro.org, philmd@redhat.com, mjt@tls.msk.ru,
imammedo@redhat.com
Subject: Re: [Qemu-devel] [PATCH v5 1/2] CODING_STYLE: specify the indent rule for multiline code
Date: Fri, 1 Mar 2019 10:55:22 +0100 [thread overview]
Message-ID: <20190301095522.65dzdgcwq7ftk5wr@steredhat> (raw)
In-Reply-To: <20190301020147.18567-2-richardw.yang@linux.intel.com>
On Fri, Mar 01, 2019 at 10:01:46AM +0800, Wei Yang wrote:
> We didn't specify the indent rule for multiline code here, which may
> mislead users. And in current code, the code use various styles.
>
> Add this rule in CODING_STYLE to make sure this is clear to every one.
>
> Signed-off-by: Wei Yang <richardw.yang@linux.intel.com>
> Suggested-by: Igor Mammedov <imammedo@redhat.com>
>
> ---
> v5:
> * different rules -> various styles
> * describe function variants separately
> * take struct out
> v4:
> * widths -> width
> * add an exception example for function
> v3:
> * misleading -> mislead
> * add comma after arg2 in example
> v2:
> * rephrase changelog suggested by Eric Blake
> - remove one redundant line
> - fix some awkward grammar
> - add { ; at the end of example
> ---
> CODING_STYLE | 39 +++++++++++++++++++++++++++++++++++++++
> 1 file changed, 39 insertions(+)
>
> diff --git a/CODING_STYLE b/CODING_STYLE
> index ec075dedc4..e175e6ea9a 100644
> --- a/CODING_STYLE
> +++ b/CODING_STYLE
> @@ -29,6 +29,45 @@ Spaces of course are superior to tabs because:
>
> Do not leave whitespace dangling off the ends of lines.
>
> +1.1 Multiline Indent
> +
> +There are several places where indent is necessary:
> +
> + - if/else
> + - while/for
> + - function definition & call
> +
> +When breaking up a long line to fit within line width, we need a proper indent
> +for the following lines.
> +
> +In case of if/else, while/for, align the secondary lines just after the
> +opening parenthesis of the first.
> +
> +For example:
> +
> + if (a == 1 &&
> + b == 2) {
> +
> + while (a == 1 &&
> + b == 2) {
> +
> +In case of function, there are several variants:
> +
> + * 4 spaces indent from the beginning
> + * align the secondary lines just after the opening parenthesis of the
> + first
> +
> +For example:
> +
> + do_something(x, y,
> + z);
> +
> + do_something(x, y,
> + z);
> +
> + do_something(x, do_another(y,
> + z);
Should we close another parenthesis after the "z"?
The rest LGTM!
Thanks,
Stefano
next prev parent reply other threads:[~2019-03-01 9:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 2:01 [Qemu-devel] [PATCH v5 0/2] CODING_STYLE: trivial update Wei Yang
2019-03-01 2:01 ` [Qemu-devel] [PATCH v5 1/2] CODING_STYLE: specify the indent rule for multiline code Wei Yang
2019-03-01 9:55 ` Stefano Garzarella [this message]
2019-03-02 11:13 ` Wei Yang
2019-03-01 2:01 ` [Qemu-devel] [PATCH v5 2/2] CODING_STYLE: indent example code as all others Wei Yang
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=20190301095522.65dzdgcwq7ftk5wr@steredhat \
--to=sgarzare@redhat.com \
--cc=imammedo@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=richardw.yang@linux.intel.com \
/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).