public inbox for
 help / color / mirror / Atom feed
From: Kris Van Hees <>
To: Jan Kratochvil <>
Cc: Tom Tromey <>, Frysk List <>
Subject: Re: Roadmap beginnings
Date: Fri, 11 Jul 2008 23:11:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Fri, Jul 11, 2008 at 10:55:31PM +0200, Jan Kratochvil wrote:
> Hi,
> while IMO definitely not much important right now but
> On Fri, 11 Jul 2008 21:53:28 +0200, Tom Tromey wrote:
> > As I mentioned in the earlier note, we want to provide scripting
> > support
> (dot)
> > based on Python.  From our perspective, Python is the best
> > choice because it is popular and generally acceptable.
> This is already your personal bias, it may be worth to design the scripting
> support easy enough to add more language bindings there (such as Perl XS).
> (I do not track your GDB patches to say more about them.)

I would expect that any even vaguely successful implementation would be
sufficiently api/library based that scripting language support us a matter
of proving the correct bindings.  I.e. pretty much any scripting language
should be possible.  Any attempt to tie it to a specific scripting language
is likely to allow implementation details to bleed into the core, which
would be a major limitation.

So, perhaps we should primarily focus on the actual debugging core?  That
doesn't exclude the use of a specific chosen language to provide at least
a prototype of an interface to interact with the core for testing purposes
(and possibly later on as a more production-level interface), but we should
be very careful not to introduce strong ties that can prove to be a major
limitation later on.


  parent reply	other threads:[~2008-07-11 23:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-11 19:53 Tom Tromey
2008-07-11 20:56 ` Jan Kratochvil
2008-07-11 21:37   ` Tom Tromey
2008-07-11 21:54     ` Daniel Jacobowitz
2008-07-11 23:11   ` Kris Van Hees [this message]
2008-07-11 21:53 ` Daniel Jacobowitz
2008-07-14 16:34   ` Tom Tromey
2008-07-14 16:45     ` Daniel Jacobowitz
2008-07-14 16:58       ` Phil Muldoon
2008-07-14 17:09         ` Daniel Jacobowitz
2008-07-14 17:19     ` Ian Lance Taylor
2008-07-14 17:34       ` Daniel Jacobowitz
2008-07-14 18:04         ` Tom Tromey
2008-07-14 18:12           ` Daniel Jacobowitz
2008-07-14 18:11         ` Ian Lance Taylor
2008-07-14 17:35       ` Tom Tromey
2008-07-14 18:13         ` Ian Lance Taylor
2008-07-22 20:29   ` Debugger Work (Was: Roadmap beginnings) Tom Tromey
2008-07-11 22:48 ` Roadmap beginnings Phil Muldoon

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).