Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Paul Koning <pkoning@equallogic.com>
To: jimb@red-bean.com
Cc: eliz@gnu.org, gdb@sourceware.org
Subject: Re: Using XML in GDB?
Date: Sun, 29 Jan 2006 04:27:00 -0000	[thread overview]
Message-ID: <17371.33866.703000.785852@gargle.gargle.HOWL> (raw)
In-Reply-To: <8f2776cb0601272233u1e7062d3k7fea5baac352c150@mail.gmail.com>

>>>>> "Jim" == Jim Blandy <jimb@red-bean.com> writes:

 Jim> I believe XML has better support in Python and Perl and Ruby and
 Jim> Java and that lot than ASN.1.

Maybe.  I've done some battle with DOM::XML:: in Perl.  It may be ok
if you want to parse XML-encoded documents; that's what it appears to
be for.  But the documentation is very feeble, and I found it to be a
nightmare when I tried to use it to parse something that wasn't a
document.   So I wouldn't necessarily say that XML Is "supported" in
Perl.  

Maybe the Python XML package is better -- gotta try that one of these
days. 

BER/DER is that it's very simple, so even if the support isn't there
yet that may not be a big issue.

 Jim> Bob Rossi mentioned issues with null characters in XML: it
 Jim> really is a text format; you're not supposed to put binary blobs
 Jim> in there at all, except as CDATA (which makes the data much
 Jim> bigger).  If you're trying to put binary data in XML, you're on
 Jim> the wrong train.

Exactly.  Conversely, ASN.1 has good data type support, including
binary types of all kinds.  

       paul


  parent reply	other threads:[~2006-01-28 14:48 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
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 [this message]
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=17371.33866.703000.785852@gargle.gargle.HOWL \
    --to=pkoning@equallogic.com \
    --cc=eliz@gnu.org \
    --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