From: Roland McGrath <mcgrathr@google.com>
To: "binutils@sourceware.org" <binutils@sourceware.org>
Subject: [COMMITTED PATCH] gold: be consistent in struct vs class for forward decl
Date: Fri, 11 Oct 2013 17:39:00 -0000 [thread overview]
Message-ID: <CAB=4xhpdwRZwWzjE_qKwwNufeBuR0OR=j9PDBNQP8BtD7tYeaw@mail.gmail.com> (raw)
Committed as obvious enough, to trunk and 2.24 branch. This makes the one
straggler consistent with all the other forward declarations of classes
whose actual definitions are done with 'struct'.
Thanks,
Roland
gold/
2013-10-11 Roland McGrath <mcgrathr@google.com>
* archive.h: Use struct rather than class for forward declaration
of Read_symbols_data.
--- a/gold/archive.h
+++ b/gold/archive.h
@@ -1,6 +1,6 @@
// archive.h -- archive support for gold -*- C++ -*-
-// Copyright 2006, 2007, 2008, 2010, 2011 Free Software Foundation, Inc.
+// Copyright 2006, 2007, 2008, 2010, 2011, 2013 Free Software Foundation, Inc.
// Written by Ian Lance Taylor <iant@google.com>.
// This file is part of gold.
@@ -40,7 +40,7 @@ class Input_group;
class Layout;
class Symbol_table;
class Object;
-class Read_symbols_data;
+struct Read_symbols_data;
class Input_file_lib;
class Incremental_archive_entry;
reply other threads:[~2013-10-11 17:39 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='CAB=4xhpdwRZwWzjE_qKwwNufeBuR0OR=j9PDBNQP8BtD7tYeaw@mail.gmail.com' \
--to=mcgrathr@google.com \
--cc=binutils@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).