From: Stan Shebs <stanshebs@earthlink.net>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] Add dll trampoline code handling for windows 64bit
Date: Wed, 14 Mar 2012 23:54:00 -0000 [thread overview]
Message-ID: <4F612FBE.10405@earthlink.net> (raw)
In-Reply-To: <20120314210310.GJ2853@adacore.com>
On 3/14/12 2:03 PM, Joel Brobecker wrote:
>> There is a script called gdb_indent.sh in gdb's root dir. I applied
>> it on amd64-windows-nat.c ahead of getting out my patch thinking
>> that this would be the correct way. Some misunderstanding as it
>> produced most of your indention concerns.
> That is very odd, the script should indeed indent the sources
> in a way that follows the GNU Coding Standards. Perhaps we are
> missing some parameters in the call to that script that override
> certain defaults that may no longer match our standards. But FWIW,
> we have rarely used that script in the past few years. I think
> that this is because GNU indent, the tool that it uses underneath,
> isn't very smart and often produces a layout that's worse than
> what a human would produce.
>
I've never been able to get indent to produce exactly the same results
as Emacs' indent, even though in theory they are using the same
algorithm with the same parameters.
Probably the best recommendation for contributors is to use Emacs
indent-region on their new code fragments, and to leave everything else
in the file alone.
Stan
next prev parent reply other threads:[~2012-03-14 23:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 20:38 Roland Schwingel
2012-03-14 21:03 ` Joel Brobecker
2012-03-14 23:54 ` Stan Shebs [this message]
2012-03-15 14:27 ` Tom Tromey
2012-03-15 15:26 ` Joel Brobecker
-- strict thread matches above, loose matches on Subject: below --
2012-03-14 13:36 Roland Schwingel
2012-03-14 15:34 ` Tom Tromey
2012-03-14 16:13 ` Joel Brobecker
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=4F612FBE.10405@earthlink.net \
--to=stanshebs@earthlink.net \
--cc=gdb-patches@sourceware.org \
/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