From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [ANNOUNCEMENT] GDB 8.1 released!
Date: Tue, 06 Feb 2018 17:02:00 -0000 [thread overview]
Message-ID: <5702aae7-7f3e-3ec4-3248-695f87ec3fae@redhat.com> (raw)
In-Reply-To: <20180202154032.6d2e6ig3h6xnfm55@adacore.com>
On 02/02/2018 03:40 PM, Joel Brobecker wrote:
> We could even split the languages section off from the last paragraph
> into its own section, vis:
>
> | What is GDB?
> | ------------
> |
> | GDB, the GNU Project debugger, allows you to see what is going on
> | `inside' another program while it executes -- or what another program
> | was doing at the moment it crashed.
> |
> | GDB can do four main kinds of things (plus other things in support of
> | these) to help you catch bugs in the act:
> |
> | * Start your program, specifying anything that might affect its behavior.
> | * Make your program stop on specified conditions.
> | * Examine what has happened, when your program has stopped.
> | * Change things in your program, so you can experiment with correcting
> | the effects of one bug and go on to learn about another.
> |
> | Those programs might be executing on the same machine as GDB (native)
> | or on another machine (remote).
Maybe add "or on a simulator".
> GDB can run on most popular UNIX and | Microsoft Windows variants.
Maybe add macOS here.
> |
> | What Languages does GDB Support?
> | --------------------------------
> |
> | GDB supports the following languages (in alphabetical order):
> | * Ada
> | * Assembly
> | * C
> | * C++
> | * D
> | * Fortran
> | * Go
> | * Objective-C
> | * OpenCL
> | * Modula-2
> | * Pascal
> | * Rust
>
Sounds good to me.
Yeah. I don't have a strong opinion there though I lean on listing
all as it avoids singling out anyone/any project and coming up with
some kind of metric to decide which ones are important. Since it's
a graphically separated list with some markup, not some
paragraph-contributing-to-the-size-of-a-hard-to-read-wall-of-text, those
who don't care about the list can just quickly and easily move their
eyes past it in a split second. I.e., I don't think 10 vs 20 entries
makes a difference in terms of readability.
> As explained above, I fear that having this exhuastive list might
> attract attention to regions of GDB that might have bitrotted a bit.
I think not listing active languages is worse than also listing
bitrotted languages, so I think on balance it's still better.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2018-02-06 17:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <announce.20180131043049.5FCFA832FF@joel.gnat.com>
2018-02-01 13:10 ` Pedro Alves
2018-02-02 15:40 ` Joel Brobecker
2018-02-06 17:02 ` Pedro Alves [this message]
2018-02-09 4:24 ` [pushed] GDB WWW main page adjustements (was: "Re: [ANNOUNCEMENT] GDB 8.1 released!") Joel Brobecker
2018-02-09 13:02 ` [pushed] GDB WWW main page adjustements Pedro Alves
2018-02-09 13:20 ` 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=5702aae7-7f3e-3ec4-3248-695f87ec3fae@redhat.com \
--to=palves@redhat.com \
--cc=brobecker@adacore.com \
--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