From: Joseph Myers <joseph@codesourcery.com>
To: Marek Polacek <polacek@redhat.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, Jason Merrill <jason@redhat.com>
Subject: Re: Split c-common.c?
Date: Tue, 27 Sep 2016 23:10:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1609272243420.17432@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20160926132207.GI3223@redhat.com>
On Mon, 26 Sep 2016, Marek Polacek wrote:
> Before I spend time on this, I wanted to check if you consider this a good
> idea. Since c-common.c has grown a lot and is quite large now, I think we
> might split it into c-warn.c, where various warning routines would go. What do
> you think?
If you have a logical division of c-common.c into different areas of
functionality, splitting them into separate files makes sense.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2016-09-27 22:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 13:34 Marek Polacek
2016-09-26 13:38 ` Jakub Jelinek
2016-09-26 13:42 ` Marek Polacek
2016-09-26 15:15 ` Jeff Law
2016-09-27 15:10 ` Jason Merrill
2016-09-27 23:10 ` Joseph Myers [this message]
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=alpine.DEB.2.20.1609272243420.17432@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=polacek@redhat.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).