From: "Guillermo E. Martinez" <guillermo.e.martinez@oracle.com>
To: libabigail@sourceware.org
Subject: [PATCH 0/3] Some improvements in ctf-reader.
Date: Wed, 17 Nov 2021 20:56:03 -0600 [thread overview]
Message-ID: <20211118025606.554809-1-guillermo.e.martinez@oracle.com> (raw)
Hello libabigail team,
These patches contains some possible improvements for
the ctf-reader.
I really appreciate your comments :-).
Kind regards,
Guillermo
Guillermo E. Martinez (3):
ctf-reader: Use argument by reference reading the context
ctf-reader: Use smart pointers in create_read_context
ctf-reader: Use ABG_ASSERT instead of assert
include/abg-ctf-reader.h | 11 +++++++----
src/abg-ctf-reader.cc | 10 ++++++----
tools/abidiff.cc | 22 ++++++++++++----------
tools/abilint.cc | 10 +++++-----
4 files changed, 30 insertions(+), 23 deletions(-)
--
2.33.0
next reply other threads:[~2021-11-18 2:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 2:56 Guillermo E. Martinez [this message]
2021-11-18 2:56 ` [PATCH 1/3] ctf-reader: Use argument by reference reading the context Guillermo E. Martinez
2021-11-18 17:26 ` Dodji Seketeli
2021-11-18 23:09 ` Guillermo Martinez
2021-11-18 23:23 ` [PATCH v2 0/3] Some improvements in ctf-reader Guillermo E. Martinez
2021-11-18 23:23 ` [PATCH 1/3] ctf-reader: Use argument by reference reading the context Guillermo E. Martinez
2021-11-23 14:26 ` Dodji Seketeli
2021-11-18 23:23 ` [PATCH 2/3] ctf-reader: Use smart pointers in create_read_context Guillermo E. Martinez
2021-11-23 14:35 ` Dodji Seketeli
2021-11-23 15:42 ` Guillermo Martinez
2021-11-18 23:23 ` [PATCH 3/3] ctf-reader: Use ABG_ASSERT instead of assert Guillermo E. Martinez
2021-11-23 14:51 ` Dodji Seketeli
2021-11-18 3:01 [PATCH 0/3] Some improvements in ctf-reader Guillermo E. Martinez
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=20211118025606.554809-1-guillermo.e.martinez@oracle.com \
--to=guillermo.e.martinez@oracle.com \
--cc=libabigail@sourceware.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.
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).