public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Doug Evans <xdje42@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH, doc RFA] Add guile gdb parameter support
Date: Tue, 27 May 2014 14:43:00 -0000	[thread overview]
Message-ID: <CAP9bCMRXEQ9bOsYGRjVG4MqJW9P_5tMCXwt3TD5vP_uU4CW+MQ@mail.gmail.com> (raw)
In-Reply-To: <87lhtnd2q9.fsf@gnu.org>

On Tue, May 27, 2014 at 1:50 AM, Ludovic Courtès <ludo@gnu.org> wrote:
> Doug Evans <xdje42@gmail.com> skribis:
>
>> +@c TODO line length
>
> You can use @ at the end of line to denote a continuation.  :-)

"works for me"

>> +@deffn {Scheme Procedure} (make-parameter! name @r{[}#:command-class command-class@r{]} @r{[}#:parameter-type parameter-type{]} @r{[}#:enum-list enum-list@r{]} @r{[}#:set-func set-func{]} @r{[}#:show-func show-func{]} @r{[}#:doc doc{]} @r{[}#:set-doc set-doc{]} @r{[}#:show-doc show-doc{]} @r{[}#:initial-value initial-value{]})
>
> It would seem more natural if this were split into two things:
>
>   1. ‘make-parameter’, which returns a new <gdb:parameter>;
>   2. ‘register-parameter!’, which calls ‘add_setshow_generic’.
>
> WDYT?
>
> Ludo’.
>

I like it!

  reply	other threads:[~2014-05-27 14:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-21 19:41 Doug Evans
2014-05-22 15:46 ` Eli Zaretskii
2014-05-26 22:03 ` Ludovic Courtès
2014-05-26 22:23   ` Doug Evans
2014-05-27  7:01     ` Ludovic Courtès
2014-05-27  8:51 ` Ludovic Courtès
2014-05-27 14:43   ` Doug Evans [this message]
2014-06-02  3:13     ` Doug Evans
2014-06-02  8:31       ` Ludovic Courtès
2014-06-02 15:21         ` Doug Evans
2014-06-02 20:50           ` Ludovic Courtès
2014-06-02 15:41       ` Eli Zaretskii
2014-06-03  9:02         ` 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=CAP9bCMRXEQ9bOsYGRjVG4MqJW9P_5tMCXwt3TD5vP_uU4CW+MQ@mail.gmail.com \
    --to=xdje42@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).