From: Joel Brobecker <brobecker@gnat.com>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb@sources.redhat.com
Subject: Re: Coding style
Date: Fri, 02 May 2003 17:32:00 -0000 [thread overview]
Message-ID: <20030502173219.GK992@gnat.com> (raw)
In-Reply-To: <200305021010.h42AAgOQ030687@elgar.kettenis.dyndns.org>
> I know that the GNU coding standards say that one should not use too
> many of those, but I think there are good reasons to keep with the
> tradition of seperating the declaration of local variables from
> geneuine code by an empty line, e.g.:
I agree with Mark.
--
Joel
next prev parent reply other threads:[~2003-05-02 17:32 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 [this message]
2003-05-02 18:46 ` Andrew Cagney
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=20030502173219.GK992@gnat.com \
--to=brobecker@gnat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).