From: Paul Schlie <schlie@comcast.net>
To: Jim Blandy <jimb@red-bean.com>
Cc: <gdb@sourceware.org>
Subject: Re: Using XML in GDB?
Date: Sun, 29 Jan 2006 23:24:00 -0000 [thread overview]
Message-ID: <C001C857.CCC9%schlie@comcast.net> (raw)
In-Reply-To: <8f2776cb0601282027k53f2ae04je61b4208250348f9@mail.gmail.com>
> From: Jim Blandy <jimb@red-bean.com>
>> On 1/28/06, Paul Schlie <schlie@comcast.net> wrote:
>>> From: Jim Blandy <jimb@red-bean.com>
>>> I think if you're going to have structured data, something like
>>> XML or ASN.1 is the way to go. (I'd actually prefer to say "lisp
>>> s-expressions", but then nobody would speak to me any more. :) )
>>
>> - Actually I'd have thought s-expression structured data would be a
>> vastly superior choice relative either perverted (IMHO) alternative.
>
> S-expressions are great if you've already got a lisp interpreter
> around. If GDB had Guile integrated into it, making all this work
> would be so easy we'd barely bother to have a conversation about it.
> But our audience is more comfortable with Python, Ruby, and Perl; I
> think a syntax that is well-supported by those tools is a better
> choice.
- sorry, thought the objective only likely necessitated a static parse of
a hierarchical definition composed of likely just strings and integers.
> It was a toss-off joke; I didn't mean to distract attention from
> Daniel's proposal. We can have a GDB extension language discussion
> on a separate thread, if people are interested.
- I'm admittedly partial to scheme.
next prev parent reply other threads:[~2006-01-29 6:18 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-29 4:33 Paul Schlie
2006-01-29 6:18 ` Jim Blandy
2006-01-29 23:21 ` Daniel Jacobowitz
2006-01-29 23:24 ` Paul Schlie [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-26 7:01 Daniel Jacobowitz
2006-01-26 12:45 ` Andrew STUBBS
2006-01-26 13:41 ` Daniel Jacobowitz
2006-01-26 16:24 ` Andrew STUBBS
2006-01-26 16:41 ` Daniel Jacobowitz
2006-01-26 17:34 ` Paul Koning
2006-01-26 17:44 ` Andrew STUBBS
2006-01-26 18:55 ` Daniel Jacobowitz
2006-01-26 21:05 ` Mark Kettenis
2006-01-26 21:26 ` Daniel Jacobowitz
2006-01-26 21:57 ` Mark Kettenis
2006-01-26 22:02 ` Daniel Jacobowitz
2006-01-26 22:32 ` Bob Rossi
2006-01-26 20:39 ` Mark Kettenis
2006-01-26 20:43 ` Bob Rossi
2006-01-26 21:41 ` Mark Kettenis
2006-01-26 20:52 ` Daniel Jacobowitz
2006-01-26 21:12 ` Bob Rossi
2006-01-27 0:47 ` Bob Rossi
2006-01-27 18:04 ` Eli Zaretskii
2006-01-27 18:41 ` Daniel Jacobowitz
2006-01-27 18:57 ` Eli Zaretskii
2006-01-27 19:06 ` Paul Koning
2006-01-28 6:33 ` Daniel Jacobowitz
2006-01-28 13:54 ` Jim Blandy
2006-01-29 4:09 ` Eli Zaretskii
2006-01-29 4:27 ` Paul Koning
2006-01-28 5:24 ` Daniel Jacobowitz
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=C001C857.CCC9%schlie@comcast.net \
--to=schlie@comcast.net \
--cc=gdb@sourceware.org \
--cc=jimb@red-bean.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).