Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <xdje42@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] record_latest_value: Call release_value_or_incref instead of release_value
Date: Mon, 03 Mar 2014 16:20:00 -0000	[thread overview]
Message-ID: <CAP9bCMQCgSFYo-=G_exdPAhAWVisNRJn0wizgJV2vWCobbXCUA@mail.gmail.com> (raw)
In-Reply-To: <20140303132336.GC4893@adacore.com>

On Mon, Mar 3, 2014 at 5:23 AM, Joel Brobecker <brobecker@adacore.com> wrote:
>> --8<---------------cut here---------------start------------->8---
>> (gdb) guile (use-modules (gdb))
>
> Following the example of Python, shouldn't this be implicit?
>
>> (gdb) guile (history-append! (make-value 42))

We had a discussion of this on the #guile irc channel, and I couldn't
find anyone who thought it should be implicit.

Plus we also had a discussion of whether the symbols should have a
builtin prefix, e.g., to avoid collisions like the one with symbol?
that ludo mentions.
E.g., gdb:symbol? instead of symbol?

I couldn't find anyone who advocated for a builtin prefix, and Guile
provides the ability to add one when importing:
(use-modules ((gdb) #:renamer (symbol-prefix-proc 'gdb:)))


  parent reply	other threads:[~2014-03-03 16:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-03  6:00 Doug Evans
2014-03-03  6:02 ` Doug Evans
2014-03-03  9:17 ` Ludovic Courtès
2014-03-03 13:23   ` Joel Brobecker
2014-03-03 15:50     ` Ludovic Courtès
2014-03-03 16:20     ` Doug Evans [this message]
2014-03-03 16:22   ` Doug Evans
2014-03-13 16:34     ` Doug Evans

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='CAP9bCMQCgSFYo-=G_exdPAhAWVisNRJn0wizgJV2vWCobbXCUA@mail.gmail.com' \
    --to=xdje42@gmail.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=ludo@gnu.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