From: Andrew Cagney <ac131313@redhat.com>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb@sources.redhat.com
Subject: Re: Coding style
Date: Fri, 02 May 2003 18:46:00 -0000 [thread overview]
Message-ID: <3EB2BD03.8070407@redhat.com> (raw)
In-Reply-To: <200305021010.h42AAgOQ030687@elgar.kettenis.dyndns.org>
> (most notably Andrew :-)
It depends on the day of the week. Sometimes my new code contains lots
of blank lines, sometimes it doesn't.
Btw, the blank line here:
int
max_register_size (struct gdbarch *gdbarch)
{
struct regcache_descr *descr;
descr = regcache_descr (gdbarch);
return descr->max_register_size;
}
makes sense, but when contracted into:
> int
> max_register_size (struct gdbarch *gdbarch)
> {
> struct regcache_descr *descr = regcache_descr (gdbarch);
>
> return descr->max_register_size;
> }
or:
> int
> max_register_size (struct gdbarch *gdbarch)
> {
> struct regcache_descr *descr = regcache_descr (gdbarch);
> return descr->max_register_size;
> }
things get pretty arbitrary. Is "descr" a declaration or code body?
Anyway, if your new code adds blank lines, I can't remove them without
rewritting the function - the requirement to keep white space changes
separate from fixes stops this.
Andrew
PS: This is somewhat ironic, Stan was oft to complain that my code
contained too many blank lines :-)
next prev parent reply other threads:[~2003-05-02 18:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-02 10:10 Mark Kettenis
2003-05-02 17:32 ` Joel Brobecker
2003-05-02 18:46 ` Andrew Cagney [this message]
2003-05-03 9:54 ` Richard Earnshaw
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=3EB2BD03.8070407@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=kettenis@chello.nl \
/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