public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: Dodji Seketeli <dodji@seketeli.org>
To: Giuliano Procida <gprocida@google.com>
Cc: kernel-team@android.com,
	"Giuliano Procida via Libabigail" <libabigail@sourceware.org>,
	"Matthias Männich" <maennich@google.com>
Subject: Re: [PATCH 3/3] reader: Use xmlFirstElementChild/xmlNextElementSibling to iterate over children elements
Date: Mon, 03 May 2021 17:18:12 +0200	[thread overview]
Message-ID: <87tunjsv63.fsf@seketeli.org> (raw)
In-Reply-To: <8735vlthjm.fsf@seketeli.org> (Dodji Seketeli's message of "Tue,  20 Apr 2021 11:46:21 +0200")

Hello,

[...]

Dodji Seketeli <dodji@seketeli.org> a écrit:

> Hello Giuliano,
>
> Giuliano Procida <gprocida@google.com> a écrit:
>
>
>> I had a quick look and there's (at least) one place where there still a
>> direct access to ->children. The code works because there are separate
>> tests to not process wrong nodes, but it would be neater to use the first
>> element child function uniformly (as well).
>
> You are right.
>
> Below is an update of that patch that hopefully addresses your comment.
>
> Thanks.
>
> From 0a6c322f6ec8be354122c6b4cdefe6143eb568ed Mon Sep 17 00:00:00 2001
> From: Dodji Seketeli <dodji@redhat.com>
> Date: Mon, 19 Apr 2021 13:50:33 +0200
> Subject: [PATCH 3/3] reader: Use xmlFirstElementChild/xmlNextElementSibling to
>  iterate over children elements
>
> Use xmlFirstElementChild/xmlNextElementSibling to iterate over element
> children nodes rather than doing it by hand in the various for loops.
>
> 	* src/abg-reader.cc (walk_xml_node_to_map_type_ids)
> 	(read_translation_unit, read_translation_unit_from_input)
> 	(read_symbol_db_from_input, build_needed)
> 	(read_elf_needed_from_input, read_corpus_group_from_input)
> 	(build_namespace_decl, build_elf_symbol_db, build_function_decl)
> 	(build_function_type, build_array_type_def, build_enum_type_decl)
> 	(build_class_decl, build_union_decl, build_function_tdecl)
> 	(build_class_tdecl, build_type_composition)
> 	(build_template_tparameter): Use
> 	xmlFirstElementChild/xmlNextElementSibling rather than poking at
> 	xmlNode::children and looping over xmlNode::next by hand.
>
> Signed-off-by: Dodji Seketeli <dodji@redhat.com>

I have just applied these 3 patches to master.  I forgot to do this
after I posted the patches and saw no follow-up here.

Thanks for the review!

[...]

Cheers,

-- 
		Dodji

  reply	other threads:[~2021-05-03 15:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-31  9:23 [PATCH] XML reader: improve XML node traversal 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
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 [this message]
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=87tunjsv63.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).