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 jos...@codesourcery.com
