Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Bob Rossi <bob@brasko.net>
To: Mark Kettenis <mark.kettenis@xs4all.nl>, gdb@sourceware.org
Subject: Re: Using XML in GDB?
Date: Thu, 26 Jan 2006 21:12:00 -0000	[thread overview]
Message-ID: <20060126210618.GA15600@brasko.net> (raw)
In-Reply-To: <20060126204812.GA16966@nevyn.them.org>

> > > And we get all sorts of things for free; for instance, UTF-8, which will be
> > > handy if someone ever wants to include internationalized descriptions in the
> > > target description.
> > > 
> > > Does anyone have a good reason why GDB should not make use of this
> > > well-standardized format instead of inventing additional ad-hoc formats?
> > 
> > No objection to using a well-standardized format, but that probably
> > only makes sense if you're not going to write your own parser.  And I
> > really would like to avoid making GDB dependent on a library that
> > isn't standardly available on all systems we support.
> 
> I definitely have no intention of either writing my own XML parser or
> introducing an external dependence.  I am tentatively planning to
> import one of {expat, libxml2} into src/ and arranging for it to be
> built as necessary.

Daniel,

One limitation I have found using libxml is that it doesn't appreciate
you putting certain char's in the file. The NUL char has given me
trouble, and has forced me to use conversion to hex or something.

Bob Rossi


  reply	other threads:[~2006-01-26 21:05 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 [this message]
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
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=20060126210618.GA15600@brasko.net \
    --to=bob@brasko.net \
    --cc=gdb@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    /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