Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Kartik Agaram" <ak@akkartik.com>
To: "Guinevere Larsen" <guinevere@redhat.com>, "Tom Tromey" <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] RFC: gdb: redo whitespace-stripping from commands
Date: Thu, 29 May 2025 06:59:14 -0700	[thread overview]
Message-ID: <40f1b99a-b17f-4174-9ac3-cd6ee531e759@app.fastmail.com> (raw)
In-Reply-To: <80eeb206-6685-4e3e-93f7-599aa9c0c77b@redhat.com>

On Thu, May 29, 2025, at 06:53, Guinevere Larsen wrote:
> Should the name end in _p? I would think _p is for pointers, and this is 
> just a bool, but maybe I'm mistaken.

I certainly don't know what I'm doing here. I was following cagney's idea in a TODO, but that's from 2002.

I'm looking around now, and at least in the cli/ subdirectory I do see this Lisp idiom of predicates getting a _p suffix. But happy to go with whatever y'all suggest.

Thanks for the hint on subcommands, I'll try it out.

  reply	other threads:[~2025-05-29 14:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-29 12:51 Kartik K. Agaram
2025-05-29 13:36 ` Tom Tromey
2025-05-29 13:53   ` Kartik Agaram
2025-05-29 13:53   ` Guinevere Larsen
2025-05-29 13:59     ` Kartik Agaram [this message]
2025-05-29 15:35     ` Tom Tromey
2025-06-01  1:17 ` Kartik K. Agaram
2025-06-01  1:17   ` [PATCH] " Kartik K. Agaram
2025-06-02 16:30     ` Guinevere Larsen
2025-06-02 16:42       ` Kartik Agaram
2025-06-02 23:39     ` [PATCH v3] " Kartik K. Agaram
2025-06-06 16:10       ` [PATCH v4] " Kartik K. Agaram
2025-07-07 17:59         ` Kartik Agaram
2025-07-08  9:27         ` Andrew Burgess

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=40f1b99a-b17f-4174-9ac3-cd6ee531e759@app.fastmail.com \
    --to=ak@akkartik.com \
    --cc=gdb-patches@sourceware.org \
    --cc=guinevere@redhat.com \
    --cc=tom@tromey.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