Re: GDB and scripting languages - which

["Kip Macy" <kip.macy@gmail.com>]

> Accordingly, I am inclined to use multiple bindings, to include at
> least Python and GUILE.  My current design relies on GDB/MI for most
> control of GDB; I might put the MI parser on the C side of the
> interface to allow MI results to be easily converted to lists / tuples
> / et cetera in each supported language, but other than that it
> would be a fairly thin interface on top of MI.
>
> (MI isn't the most convenient interface for scripting - I'm still
> trying to figure out how it will interact with GDB's value objects, but
> it will probably build on top of varobj to do so.  The symmetry is
> nice; what you can do in scripts you ought to be able to do in a
> GUI front end to GDB too so any MI extensions useful for one
> are likely useful to the other.  However, this is the subject of
> a later discussion, not this one.)


This is what I did to add perl support and it worked fairly well. Some
work will be needed to handle exceptions gracefully on the scripting
library side. I prefer python too. However, I think it is more
important that there be *a* scripting language than that it be the
"right" one. Getting bogged down in bike-shedding is counter to
everyone's interests.

 -Kip