From: David Blaikie <dblaikie@gmail.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: Zied Guermazi <zied.guermazi@trande.de>, gdb@sourceware.org
Subject: Re: GNU style checker for GDB
Date: Mon, 8 Mar 2021 12:39:03 -0800 [thread overview]
Message-ID: <CAENS6EtgXELj1D4+Toc973y7wb8URU7Bx2YtvyBi3or1r_mEhg@mail.gmail.com> (raw)
In-Reply-To: <278d129c-f27c-c47c-3e33-4a5a85cda855@polymtl.ca>
If anyone's interested in investing some time in it, I expect clang-format
would be open to bugs/patches to support whatever formatting idioms gdb
needs.
On Mon, Mar 8, 2021 at 10:26 AM Simon Marchi via Gdb <gdb@sourceware.org>
wrote:
> On 2021-03-08 8:10 a.m., Zied Guermazi wrote:
> > hi,
> >
> > is there a style checker that I can use to detect styles issues before
> sending patches to gdb-patches@sourceware.org?
> >
> > I have the program indent installed on my machine. can it be used for
> this purpose? which options shall i use?
> >
> > Kind Regards
> >
> > Zied Guermazi
>
> People try now and then to configure tools to do this, but so
> unfortunately so far there is no tool/configuration that matches exactly
> the style we use. If I remember correctly, indent does not know C++, so
> it's not useful here. clang-format can get quite close, but not enough
> so that we can say "just run this and it will be fine".
>
> To be clear, I really wish there existed such a tool, it would simplify
> things a lot.
>
> Simon
>
>
>
next prev parent reply other threads:[~2021-03-08 20:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 13:10 Zied Guermazi
2021-03-08 17:35 ` Simon Marchi
2021-03-08 20:39 ` David Blaikie [this message]
2021-03-08 22:31 ` Simon Marchi
2021-03-08 22:39 ` David Blaikie
2021-03-08 22:53 ` Simon Marchi
2021-03-08 23:21 ` Dave Marples
2021-03-09 6:08 ` Metzger, Markus T
2021-03-10 10:32 ` Zied Guermazi
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=CAENS6EtgXELj1D4+Toc973y7wb8URU7Bx2YtvyBi3or1r_mEhg@mail.gmail.com \
--to=dblaikie@gmail.com \
--cc=gdb@sourceware.org \
--cc=simon.marchi@polymtl.ca \
--cc=zied.guermazi@trande.de \
/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).