From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Chong Yidong Newsgroups: gmane.emacs.devel Subject: Re: Problems with xml-parse-string Date: Fri, 24 Sep 2010 11:25:25 -0400 Message-ID: <87k4mb2mfu.fsf@stupidchicken.com> References: <87pqw6d7nz.fsf@stupidchicken.com> <87zkvaiked.fsf@stupidchicken.com> <87vd5ymptn.fsf@stupidchicken.com> <87vd5x7ty2.fsf@stupidchicken.com> <87vd5wo48a.fsf@stupidchicken.com> <8739t03q2g.fsf@stupidchicken.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1285342547 21730 80.91.229.12 (24 Sep 2010 15:35:47 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 24 Sep 2010 15:35:47 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Sep 24 17:35:44 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1OzAJL-0001wq-ND for ged-emacs-devel@m.gmane.org; Fri, 24 Sep 2010 17:35:44 +0200 Original-Received: from localhost ([127.0.0.1]:47477 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OzAJL-0004KE-16 for ged-emacs-devel@m.gmane.org; Fri, 24 Sep 2010 11:35:43 -0400 Original-Received: from [140.186.70.92] (port=33320 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OzAIt-00043S-HW for emacs-devel@gnu.org; Fri, 24 Sep 2010 11:35:21 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OzA9P-00085z-5L for emacs-devel@gnu.org; Fri, 24 Sep 2010 11:25:30 -0400 Original-Received: from pantheon-po43.its.yale.edu ([130.132.50.104]:56420) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OzA9O-00085l-V5 for emacs-devel@gnu.org; Fri, 24 Sep 2010 11:25:27 -0400 Original-Received: from furry (dhcp128036014154.central.yale.edu [128.36.14.154]) (authenticated bits=0) by pantheon-po43.its.yale.edu (8.12.11.20060308/8.12.11) with ESMTP id o8OFPP4E027888 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Fri, 24 Sep 2010 11:25:26 -0400 Original-Received: by furry (Postfix, from userid 1000) id B963C16D402; Fri, 24 Sep 2010 11:25:25 -0400 (EDT) In-Reply-To: (Lars Magne Ingebrigtsen's message of "Fri, 24 Sep 2010 12:49:25 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) X-YaleITSMailFilter: Version 1.2c (attachment(s) not renamed) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4-2.6 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:130783 Archived-At: Lars Magne Ingebrigtsen writes: > Chong Yidong writes: > >> If we're going to make a clean break with the old xml.el parse tree >> format, I think it makes more sense to go with sxml. > > The sxml format is even less regular than the xml.el format. What would > the advantages be to switching to sxml be? Could you elaborate? I'm looking at sxml's Wikipedia page, which has an example where Text node maps to (tag (@ (attr1 "value1") (attr2 "value2")) (nested "Text node") (empty)) This seems pretty regular to me.