Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Guinevere Larsen <guinevere@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2] gdb: add tutorial command
Date: Fri, 23 Jan 2026 16:28:02 +0200	[thread overview]
Message-ID: <864iocietp.fsf@gnu.org> (raw)
In-Reply-To: <19c407af-d5a8-49a0-9413-1d41d23c7fbf@redhat.com> (message from Guinevere Larsen on Fri, 23 Jan 2026 11:14:20 -0300)

> Date: Fri, 23 Jan 2026 11:14:20 -0300
> Cc: gdb-patches@sourceware.org
> From: Guinevere Larsen <guinevere@redhat.com>
> 
> > Isn't it strange to teach newbies that to assign a value to a
> > variable, one must use the 'print' command?  Why not "set variable"?
> 
> It is a bit strange, I suppose, but "set" (like "call") are not things I use personally, when print can do the same
> and is one fewer command to remember
> 
> And this doubles as a warning that if the user calls a function that has side-effects, those will also happen,
> and they aren't necessarily always desired by the user...
> 
> I can change it if you feel strongly that we should use "set" instead, but I find the side-effect explanation to
> be worth the unintuitiveness

I think the tutorial should teach the commands intended for their
purposes.  Some commands have side effects, but that's not newbie
stuff, IMO.

What do others think about this?

  parent reply	other threads:[~2026-01-23 14:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-22 20:28 Guinevere Larsen
2026-01-23  7:11 ` Eli Zaretskii
2026-01-23 14:14   ` Guinevere Larsen
2026-01-23 14:23     ` Arsen Arsenović
2026-01-23 14:28     ` Eli Zaretskii [this message]
2026-01-26 14:54       ` Andrew Burgess
2026-01-26 18:50         ` Guinevere Larsen
2026-01-24 11:41 ` Hannes Domani
2026-01-26 18:08   ` Guinevere Larsen
2026-01-26 16:13 ` Andrew Burgess
2026-01-27 19:39   ` Guinevere Larsen

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=864iocietp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=guinevere@redhat.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