named warnings & individual warning control

[Mark Mitchell]

DJ Delorie wrote:

> I just had an idea for a dirty hack...
> 
> Replace the warn() function with a macro that passes the FILE/LINE it
> was called from as well.  Add a pragma that lets you block messages
> based on the file/line in gcc where they're generated.  Of *course*
> they're going to change from release to release!  How could you even
> imagine otherwise? ;-)

Yes.

To me, it sounds like an expedient short-term hack to solve a customer 
problem, but not something we'd want in the FSF tree, but maybe other 
people feel differently.

-- 
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com