Re: [commit] Deprecate remaining STREQ uses

[Andrew Cagney <cagney@gnu.org>]

> Very true.  Explicit deprecation is a tool for making that part of the 
>> maintainer and contributor task far easier.  Instead of wasting time 
>> trying to track and find all the things being eliminated, the 
>> contributor and reviewer can simply keep an eye out for deprecated in 
>> their patches
> 
> 
> I'm not convinced that detecting STREQ is harder than detecting
> DEPRECATED_STREQ.

I was talking generally.  There are currently 99 deprecated methods (and 
a further 78 that are listed as potential candidates).  I don't think 
anyone could reasonably be expected to keep track of all of that, least 
of all a non-core contributor.

Anyway, I think the STREQ specific issue has been beaten to death.  I've 
now learnt a robust mechanical way of eliminating the macro and will 
endevor to shortly eliminate it.

enjoy,
Andrew