From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14430 invoked by alias); 28 Jan 2006 06:33:11 -0000 Received: (qmail 14281 invoked by uid 22791); 28 Jan 2006 06:33:10 -0000 X-Spam-Check-By: sourceware.org Received: from zproxy.gmail.com (HELO zproxy.gmail.com) (64.233.162.200) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 28 Jan 2006 06:33:09 +0000 Received: by zproxy.gmail.com with SMTP id x3so802730nzd for ; Fri, 27 Jan 2006 22:33:08 -0800 (PST) Received: by 10.36.154.20 with SMTP id b20mr3170053nze; Fri, 27 Jan 2006 22:33:07 -0800 (PST) Received: by 10.37.2.63 with HTTP; Fri, 27 Jan 2006 22:33:07 -0800 (PST) Message-ID: <8f2776cb0601272233u1e7062d3k7fea5baac352c150@mail.gmail.com> Date: Sat, 28 Jan 2006 13:54:00 -0000 From: Jim Blandy To: Paul Koning , eliz@gnu.org, gdb@sourceware.org Subject: Re: Using XML in GDB? In-Reply-To: <20060127190629.GB16811@nevyn.them.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20060126055744.GA29647@nevyn.them.org> <20060127180429.GA15726@nevyn.them.org> <17370.26869.663043.743656@gargle.gargle.HOWL> <20060127190629.GB16811@nevyn.them.org> X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-01/txt/msg00317.txt.bz2 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. :) )=20 There's no reason to re-invent all that. I believe XML has better support in Python and Perl and Ruby and Java and that lot than ASN.1. Bob Rossi mentioned issues with null characters in XML: it really is a text format; you're not supposed to put binary blobs in there at all, except as CDATA (which makes the data much bigger). If you're trying to put binary data in XML, you're on the wrong train.