This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Documentation for Scheme scripting
- From: Doug Evans <dje at sceeck dot org>
- To: Tom Tromey <tromey at redhat dot com>
- Cc: gdb-patches at sourceware dot org, eliz at gnu dot org
- Date: Mon, 9 Sep 2013 22:29:10 -0700
- Subject: Re: Documentation for Scheme scripting
- Authentication-results: sourceware.org; auth=none
- References: <CAEei7h_R2DQvWpoDBu4rhVr63QkKsrqHFu4=3Py1LaYD8=G4XQ at mail dot gmail dot com> <87k3iqj5fk dot fsf at fleche dot redhat dot com>
On Mon, Sep 9, 2013 at 10:00 AM, Tom Tromey <tromey@redhat.com> wrote:
>[...] I think it is
> unreasonable to require all Python changes to come with Scheme patches
> as well.
No disagreement there.
> 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.
How far do you think Guile vs Scheme should be pushed?
Should the command to invoke a Scheme command be named "guile" instead
of "scheme"?
Should the gdb subdirectory be gdb/guile over gdb/scheme?