Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Dave Marples <dave@marples.net>
To: gdb@sourceware.org
Subject: Re: GNU style checker for GDB
Date: Mon, 8 Mar 2021 23:21:49 +0000	[thread overview]
Message-ID: <df37cc2e-7d5d-ce6c-162b-2964b5809880@marples.net> (raw)
In-Reply-To: <CAENS6EsNPpJOog5w0xU9xgvC7REn56GaAX=WkGTQk57sn1+Qfw@mail.gmail.com>


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


  parent reply	other threads:[~2021-03-08 23:21 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 [this message]
2021-03-09  6:08           ` Metzger, Markus T via Gdb
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=df37cc2e-7d5d-ce6c-162b-2964b5809880@marples.net \
    --to=dave@marples.net \
    --cc=gdb@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