This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Another issue with diagnostic format-checker
"Zack Weinberg" <zack@codesourcery.com> writes:
| Gabriel Dos Reis <gdr@integrable-solutions.net> writes:
|
| > "Zack Weinberg" <zack@codesourcery.com> writes:
| >
| > | Gabriel Dos Reis <gdr@integrable-solutions.net> writes:
| > |
| > | > | Okay, I understand this. However, this suggests that you intend to
| > | > | compile files shared between front ends more than once, with different
| > | > | settings of GCC_DIAG_STYLE.
| > | >
| > | > Not really. Remember, the whole thing is composed of two parts
| > | >
| > | > 1) interface (.h files) translated every time they are included.
| > | > These files are also the most shared files.
| > | > This is where the attribute declarations are put.
| > | >
| > | > 2) implementation (.c files) usually translated once.
| > | >
| > | > I'm NOT proposing to translate implementation files multiple times.
| > |
| > | Then I do not see what putting -D switches in the makefile gains you
| > | over putting #defines in the relevant source files.
| >
| > It removes the inclusion order dependency and lets each front end say
| > what its "set" looks like.
|
| So does putting #defines in the relevant source files.
No, it does not. See previous discussion with Kaveh.
You're right on one point: You are not closely following the
discussion.
-- Gaby