From: Dodji Seketeli <dodji@seketeli.org>
To: Giuliano Procida <gprocida@google.com>
Cc: "Giuliano Procida via Libabigail" <libabigail@sourceware.org>,
kernel-team@android.com, "Matthias Männich" <maennich@google.com>
Subject: Re: [PATCH v2, v4] XML reader: improve XML node traversal
Date: Mon, 19 Apr 2021 15:40:48 +0200 [thread overview]
Message-ID: <87k0oytmsf.fsf@seketeli.org> (raw)
In-Reply-To: <CAGvU0H=JwQxroHeu_3JsmKzm9iCcvvJ_bkga+z6B6Q89bGQxBg@mail.gmail.com> (Giuliano Procida's message of "Fri, 16 Apr 2021 13:03:53 +0100")
Hello Giuliano,
Thanks for the your thourough response.
[...]
> And full disclosure, I've since found (a day or so ago) that the
> libxml Tree API already defines xmlFirstElementChild and
> xmlNextElementSibling which are essentially identical to the
> primitives I defined. This also gives me a boost in confidence that
> they are the right primitives for traversing the XML tree for
> libabigail.
Right. As the text/element node handling issue is addressed by the
patch I sent, I went ahead and (hopefully) address the confusion and
useless redundancy that arise from not using the xmlFirstElementChild
and xmlNextElementSibling APIs. I am thus adding two patches to that
one to use those functions instead.
[...]
> I was going to reply separately to review, but the commit below is
> quite short. I'm sure it addresses the issue of significant
> whitespace. If you haven't done so already, please test by removing
> all whitespace from all the test XML files and then running abidiff vs
> the originals. There is a short recipe for doing this in the bug
> report.
I have tested the series of 3 patches that I am going to post as reply
of this message with that script you added to the bug report at
https://sourceware.org/bugzilla/show_bug.cgi?id=27616.
There are two crashes that are unrelated to this issue at hand. That's because
libabigail doesn't (yet) support comparing decls coming from templates
and that's a known issue.
The two invocations that crash are:
build/tools/abidiff --harmless tests/data/test-read-write/test12.xml tests/data/test-read-write/test12.xml.wrung
build/tools/abidiff --harmless tests/data/test-read-write/test13.xml tests/data/test-read-write/test13.xml.wrung
Other than that, everything else seem to work.
Thank you for your time and dedication!
[...]
Cheers,
--
Dodji
next prev parent reply other threads:[~2021-04-19 13:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 9:23 [PATCH] " Giuliano Procida
2021-03-31 14:24 ` Matthias Maennich
2021-03-31 16:58 ` Giuliano Procida
2021-03-31 17:04 ` [PATCH v2] " Giuliano Procida
2021-04-06 11:48 ` Dodji Seketeli
2021-04-06 14:35 ` Giuliano Procida
2021-04-06 16:22 ` [PATCH v3] " Giuliano Procida
2021-04-06 17:39 ` [PATCH v4] " Giuliano Procida
2021-04-15 14:12 ` [PATCH v2, " Dodji Seketeli
2021-04-16 12:03 ` Giuliano Procida
2021-04-19 13:40 ` Dodji Seketeli [this message]
2021-04-19 14:00 ` Subject: [PATCH 1/3] reader: Handle 'abi-corpus' element being possibly empty Dodji Seketeli
2021-04-19 14:01 ` [PATCH 2/3] reader: Use xmlFirstElementChild and xmlNextElementSibling rather than xml::advance_to_next_sibling_element Dodji Seketeli
2021-04-19 14:03 ` [PATCH 3/3] reader: Use xmlFirstElementChild/xmlNextElementSibling to iterate over children elements Dodji Seketeli
2021-04-20 6:52 ` Giuliano Procida
2021-04-20 9:46 ` Dodji Seketeli
2021-05-03 15:18 ` Dodji Seketeli
2021-05-04 11:13 ` Giuliano Procida
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=87k0oytmsf.fsf@seketeli.org \
--to=dodji@seketeli.org \
--cc=gprocida@google.com \
--cc=kernel-team@android.com \
--cc=libabigail@sourceware.org \
--cc=maennich@google.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).