From: Eli Zaretskii <eliz@gnu.org>
To: gdb@sourceware.org
Subject: Re: Using XML in GDB?
Date: Fri, 27 Jan 2006 18:04:00 -0000 [thread overview]
Message-ID: <u8xt1efg5.fsf@gnu.org> (raw)
In-Reply-To: <20060126055744.GA29647@nevyn.them.org> (message from Daniel Jacobowitz on Thu, 26 Jan 2006 00:57:44 -0500)
> Date: Thu, 26 Jan 2006 00:57:44 -0500
> From: Daniel Jacobowitz <drow@false.org>
>
> Does anyone have a good reason why GDB should not make use of this
> well-standardized format instead of inventing additional ad-hoc formats?
I'd like to see some spec, if you please. It's hard to make up one's
mind without at least that, since XML is not the ideal format for all
and every type of communications. It has disadvantages, some of them
were already mentioned in this thread: it's very wordy, and existing
implementations are not guaranteed to exist on every supported
platform (telling users to download and install additional packages as
a prerequisite to building GDB is a mild nuisance).
So I'd like to weigh these demerits against the advantages, and that
is only possible if some kind of specification for this specific
interface which we are discussing is available.
I've read your description from May (and just re-read it now), and it
sounds like the number of different entities we need to communicate is
quite small and their structure is simple. So why did you come to the
conclusion that you needed something like XML to express that
interface?
next prev parent reply other threads:[~2006-01-27 17:41 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
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
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=u8xt1efg5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sourceware.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