From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org, Joel Brobecker <brobecker@adacore.com>
Subject: Re: [PATCH 2/3] Move file_and_directory to new file and C++-ize
Date: Sat, 4 Dec 2021 14:38:51 +0400 [thread overview]
Message-ID: <YatFO7vk+mrVPhNO@adacore.com> (raw)
In-Reply-To: <20211130013304.4135367-3-tom@tromey.com>
Hi Tom,
In addition to the comments already made about the name of the class
members, I was wondering why you were adding the following include
in this patch, since I didn't see any use of the file_and_directory.
> diff --git a/gdb/dwarf2/read.h b/gdb/dwarf2/read.h
> index fe34e3f95ae..0afcda1c3b0 100644
> --- a/gdb/dwarf2/read.h
> +++ b/gdb/dwarf2/read.h
> @@ -23,6 +23,7 @@
> #include <queue>
> #include <unordered_map>
> #include "dwarf2/comp-unit-head.h"
> +#include "dwarf2/file-and-dir.h"
> #include "dwarf2/index-cache.h"
> #include "dwarf2/section.h"
> #include "filename-seen-cache.h"
Looking at the next patch, I think perhaps this include should be moved
over to patch #3?
--
Joel
next prev parent reply other threads:[~2021-12-04 10:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 1:33 [PATCH 0/3] Refactor find_file_and_directory Tom Tromey
2021-11-30 1:33 ` [PATCH 1/3] Remove Irix case from find_file_and_directory Tom Tromey
2021-12-04 10:43 ` Joel Brobecker
2021-11-30 1:33 ` [PATCH 2/3] Move file_and_directory to new file and C++-ize Tom Tromey
2021-11-30 16:18 ` Lancelot SIX
2021-11-30 17:44 ` Tom Tromey
2021-12-04 10:38 ` Joel Brobecker [this message]
2021-12-04 18:22 ` Tom Tromey
2021-11-30 1:33 ` [PATCH 3/3] Cache the result of find_file_and_directory Tom Tromey
2021-12-04 10:42 ` Joel Brobecker
2021-12-04 18:22 ` Tom Tromey
2021-12-05 2:31 ` Simon Marchi
2021-12-05 3:46 ` Tom Tromey
2021-12-05 3:47 ` Simon Marchi
2021-12-05 20:17 ` Tom Tromey
2021-12-06 1:54 ` Simon Marchi
2021-12-07 4:30 ` Tom Tromey
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=YatFO7vk+mrVPhNO@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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).