public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] gdbsupport: rename include guard in gdb-checked-static-cast.h Date: Tue, 19 Mar 2024 14:57:38 +0000 (GMT) [thread overview] Message-ID: <20240319145738.F1C363858417@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=8695c3a693849bf6ebd3c6d0620f03bcc6429604 commit 8695c3a693849bf6ebd3c6d0620f03bcc6429604 Author: Andrew Burgess <aburgess@redhat.com> Date: Wed Mar 6 17:48:55 2024 +0000 gdbsupport: rename include guard in gdb-checked-static-cast.h I noticed in passing that the include guard in the file gdbsupport/gdb-checked-static-cast.h was wrong, it includes the word DYNAMIC when STATIC would be better, fixed in this commit. There should be no user visible changes after this commit. Diff: --- gdbsupport/gdb-checked-static-cast.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/gdbsupport/gdb-checked-static-cast.h b/gdbsupport/gdb-checked-static-cast.h index 24fa7a4ba04..97843fab225 100644 --- a/gdbsupport/gdb-checked-static-cast.h +++ b/gdbsupport/gdb-checked-static-cast.h @@ -15,8 +15,8 @@ You should have received a copy of the GNU General Public License along with this program. If not, see <http://www.gnu.org/licenses/>. */ -#ifndef COMMON_GDB_CHECKED_DYNAMIC_CAST_H -#define COMMON_GDB_CHECKED_DYNAMIC_CAST_H +#ifndef COMMON_GDB_CHECKED_STATIC_CAST_H +#define COMMON_GDB_CHECKED_STATIC_CAST_H #include "gdbsupport/traits.h" @@ -80,4 +80,4 @@ checked_static_cast (V &v) } -#endif /* COMMON_GDB_CHECKED_DYNAMIC_CAST_H */ +#endif /* COMMON_GDB_CHECKED_STATIC_CAST_H */
reply other threads:[~2024-03-19 14:57 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240319145738.F1C363858417@sourceware.org \ --to=aburgess@sourceware.org \ --cc=gdb-cvs@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: linkBe 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).