From: Doug Evans <dje@sceeck.org>
To: gdb-patches@sourceware.org, eliz@gnu.org
Subject: Documentation for Scheme scripting
Date: Sun, 08 Sep 2013 21:12:00 -0000 [thread overview]
Message-ID: <CAEei7h_R2DQvWpoDBu4rhVr63QkKsrqHFu4=3Py1LaYD8=G4XQ@mail.gmail.com> (raw)
Hi.
I'm finishing up the Scheme scripting functionality I want to have in
the first pass.
[For those not familiar with the work, I'm adding Scheme scripting
functionality to gdb that will be akin to the current Python scripting
support.]
One thing that remains is documentation.
Do folks have any preferences for how they want Scheme scripting documented?
And, any preferences for how they *not* want it done?
I can imagine making a copy of all the Python docs and just changing
spelling and such.
I'm not suggesting that's the best approach, but it is *an* approach.
From the point of view of the reader, when reading docs on Python
scripting, they might prefer *not* having to have it complicated by
reading about Scheme as well.
OTOH, duplicating all of that has its own issues.
One thing I'm hoping to avoid is doing a lot of typing only to have to
redo it all.
Speaking up now would be most welcome. :-)
Suggestions?
next reply other threads:[~2013-09-08 21:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-08 21:12 Doug Evans [this message]
2013-09-09 2:47 ` Eli Zaretskii
2013-09-09 17:00 ` Tom Tromey
2013-09-09 17:13 ` Eli Zaretskii
2013-09-10 5:30 ` Doug Evans
2013-09-10 5:29 ` Doug Evans
2013-09-10 15:25 ` Eli Zaretskii
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='CAEei7h_R2DQvWpoDBu4rhVr63QkKsrqHFu4=3Py1LaYD8=G4XQ@mail.gmail.com' \
--to=dje@sceeck.org \
--cc=eliz@gnu.org \
--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