From: Steinar Bang <sb@dod.no>
To: emacs-devel@gnu.org
Subject: Re: mapping data formats imported from C libraries
Date: Wed, 26 Nov 2014 11:41:51 +0100 [thread overview]
Message-ID: <upzcwq6ip7kg.fsf@dod.no> (raw)
In-Reply-To: m3k32j6wgy.fsf@stories.gnus.org
>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org>:
> The Emacs DOM is quite non-sucky. It's just a tree.
> (thing ((attrib . value)) (foo) (bar))
Nice. How do you get to that tree from libxml2? Is it parsed into the
libxml2 DOM first and then transferred into the lisp structure?
If so, is the libxml2 tree kept in memory as well, or is it free'd? Or
is the lisp structure a thin wrapper over the libxml2 native tree?
Or is the XML stream parsed by libxml2 directly into the lisp structure?
Ie. the lisp structure is the only in-memory representation of the DOM?
next prev parent reply other threads:[~2014-11-26 10:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-23 15:18 DOM manipulation functions Lars Magne Ingebrigtsen
2014-11-23 15:58 ` joakim
2014-11-23 15:59 ` Rüdiger Sonderfeld
2014-11-23 16:01 ` Lars Magne Ingebrigtsen
2014-11-23 16:52 ` Steinar Bang
2014-11-24 0:26 ` Leo Liu
2014-11-25 9:12 ` mapping data formats imported from C libraries (was: DOM manipulation functions) Ted Zlatanov
2014-11-25 15:54 ` mapping data formats imported from C libraries Lars Magne Ingebrigtsen
2014-11-25 16:27 ` Ted Zlatanov
2014-11-25 16:32 ` Lars Magne Ingebrigtsen
2014-11-25 16:40 ` Ted Zlatanov
2014-11-25 17:06 ` Lars Magne Ingebrigtsen
2014-11-26 10:41 ` Steinar Bang [this message]
2014-11-26 15:51 ` Lars Magne Ingebrigtsen
2014-11-26 19:57 ` Steinar Bang
2014-11-26 20:00 ` Lars Magne Ingebrigtsen
2014-11-26 12:59 ` Ted Zlatanov
2014-11-26 15:56 ` Lars Magne Ingebrigtsen
2014-11-26 16:48 ` Ted Zlatanov
2014-11-23 18:45 ` DOM manipulation functions raman
2014-11-25 11:01 ` Nicolas Richard
2014-11-26 18:44 ` Lars Magne Ingebrigtsen
2014-11-26 19:42 ` Ted Zlatanov
2014-11-26 19:44 ` Lars Magne Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=upzcwq6ip7kg.fsf@dod.no \
--to=sb@dod.no \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).