Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <xdje42@gmail.com>
To: gdb-patches@sourceware.org, guile-user@gnu.org
Subject: [PATCH 00/13] script language API for GDB
Date: Thu, 05 Dec 2013 17:06:00 -0000	[thread overview]
Message-ID: <m3pppb2ppe.fsf@sspiff.org> (raw)

Hi.

My patch set to add a scripting API to GDB is ready for submission.
It sets things up so that adding Guile scripting is straightforward.
I've cc'd guile-users to apprise them of my progress.
I'll spare them the actual set of patches here,
though I plan to cc them when submitting the Guile port,
their input will be helpful.
The actual Guile port is ready ... just have some more docs to write. :-)

This patch set also has a nice effect of formalizing the interface from
GDB to Python (one aspect of which is that it removes the need for
a lot if #ifdef HAVE_PYTHON's, and it removes all the little stubs that
had to be provided when GDB was compiled --without-python).

The main patches are 02 and 03.
02 adds scripting.c, scripting.h, and scripting-priv.h.
03 updates python.c, python.h, and python-internal.h.
The rest are pretty-straightforward.

A lot of the change is mechanical:
- I want to have each ops "method" named ${lang}_${method_name}.
- Plus I want to have each API entry point have something in its
  name that says "I am a scripting API entry point".
  My first attempt used slang_ but that was thought to have
  to much potential confusion with the slang scripting language.
  Instead I've taken a minimalist approach and added "script"
  to the function name.
  E.g., apply_val_pretty_printer -> apply_val_script_pretty_printer
- Then I needed to move the interface enums defined in python.h
  out and make the values have non-python-specific names.

I'm going to wait until after 7.7 has been branched
before checking anything in of course.


             reply	other threads:[~2013-12-05 17:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-05 17:06 Doug Evans [this message]
2013-12-06  5:51 ` Doug Evans
2013-12-06 12:57   ` Phil Muldoon
2013-12-06 16:07     ` Doug Evans
2013-12-20 16:26       ` Tom Tromey
2013-12-23 17:40         ` Doug Evans
2013-12-23 21:54           ` Tom Tromey
2013-12-23 21:58             ` 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=m3pppb2ppe.fsf@sspiff.org \
    --to=xdje42@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=guile-user@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