From: Zied Guermazi <zied.guermazi@trande.de>
To: "Metzger, Markus T" <markus.t.metzger@intel.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: GNU style checker for GDB
Date: Wed, 10 Mar 2021 11:32:24 +0100 [thread overview]
Message-ID: <8f1db69a-32e8-02f8-5e16-f927bc3c0d66@trande.de> (raw)
In-Reply-To: <DM5PR11MB16906592490758321C783585DE929@DM5PR11MB1690.namprd11.prod.outlook.com>
hi
thanks Markus, the script was helpful spotting style mismatch.
can this script be referred from
https://sourceware.org/gdb/wiki/Internals%20Coding-Standards ?
Kind Regards
Zied Guermazi
On 09.03.21 07:08, Metzger, Markus T wrote:
> There's gcc.git/contrib/check_GNU_style.sh.
>
> Regards,
> Markus.
>
>> -----Original Message-----
>> From: Gdb <gdb-bounces@sourceware.org> On Behalf Of Dave Marples
>> Sent: Dienstag, 9. März 2021 00:22
>> To: gdb@sourceware.org
>> Subject: Re: GNU style checker for GDB
>>
>>
>> On 08/03/2021 22:39, David Blaikie via Gdb wrote:
>>> I think if you can point to a widely used style (the gdb (& binutils more
>>> generally?) codebase) there's probably going to be a fair bit of
>>> sympathy/understanding there.
>> It seems to me that this is a problem screaming out for Machine
>> Learning. I see so many projects that don't have a formal style guide
>> but have a "please format your code like the rest of the code is already
>> formatted 'cos we like that" policy. Nothing wrong with that policy at
>> all, except that it's obviously incredibly difficult to automate.
>>
>> It would make a really nice final year undergrad project for someone to
>> train up an AI on the style of an existing codebase, then use the
>> developed knowledge to edit new code into that same format.
>>
>> ...anyone got any suitably smart final year students that would bite on
>> a project like that? I can think of plenty of projects that could make
>> use of it!
>>
>> DAVE
> Intel Deutschland GmbH
> Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
> Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
> Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
> Chairperson of the Supervisory Board: Nicole Lau
> Registered Office: Munich
> Commercial Register: Amtsgericht Muenchen HRB 186928
--
*Zied Guermazi*
founder
Trande UG
Leuschnerstraße 2
69469 Weinheim/Germany
Mobile: +491722645127
mailto:zied.guermazi@trande.de
*Trande UG*
Leuschnerstraße 2, D-69469 Weinheim; Telefon: +491722645127
Sitz der Gesellschaft: Weinheim- Registergericht: AG Mannheim HRB 736209
- Geschäftsführung: Zied Guermazi
*Confidentiality Note*
This message is intended only for the use of the named recipient(s) and
may contain confidential and/or privileged information. If you are not
the intended recipient, please contact the sender and delete the
message. Any unauthorized use of the information contained in this
message is prohibited.
prev parent reply other threads:[~2021-03-10 10:33 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 via Gdb
2021-03-08 20:39 ` David Blaikie via Gdb
2021-03-08 22:31 ` Simon Marchi via Gdb
2021-03-08 22:39 ` David Blaikie via Gdb
2021-03-08 22:53 ` Simon Marchi via Gdb
2021-03-08 23:21 ` Dave Marples
2021-03-09 6:08 ` Metzger, Markus T via Gdb
2021-03-10 10:32 ` Zied Guermazi [this message]
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=8f1db69a-32e8-02f8-5e16-f927bc3c0d66@trande.de \
--to=zied.guermazi@trande.de \
--cc=gdb@sourceware.org \
--cc=markus.t.metzger@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