From: Tom Tromey <tromey@redhat.com>
To: Doug Evans <dje@sceeck.org>
Cc: gdb-patches@sourceware.org, eliz@gnu.org
Subject: Re: Documentation for Scheme scripting
Date: Mon, 09 Sep 2013 17:00:00 -0000 [thread overview]
Message-ID: <87k3iqj5fk.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CAEei7h_R2DQvWpoDBu4rhVr63QkKsrqHFu4=3Py1LaYD8=G4XQ@mail.gmail.com> (Doug Evans's message of "Sun, 8 Sep 2013 14:12:46 -0700")
>>>>> "Doug" == Doug Evans <dje@sceeck.org> writes:
Doug> I can imagine making a copy of all the Python docs and just changing
Doug> spelling and such.
Surely the Scheme API will not be just a simple copy of the Python API.
Even if that is the intent it will not be true since I think it is
unreasonable to require all Python changes to come with Scheme patches
as well.
I think the Scheme docs have to just be a whole separate section
spelling everything out in Scheme terms.
Though I would like to say now that this isn't really Scheme we're
talking about, but Guile. There are differences. I think it would be
best to be explicit about that in the docs.
Tom
next prev parent reply other threads:[~2013-09-09 17:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-08 21:12 Doug Evans
2013-09-09 2:47 ` Eli Zaretskii
2013-09-09 17:00 ` Tom Tromey [this message]
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=87k3iqj5fk.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=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