Code auditing

[Nathan Myers]

When I audited the libstdc++-v3 library recently for un-thread-safe
initializations of static local variables, I used find(1) to identify
C++ source files.

According to the (then) header policy all the files with any real
code in them should have had a filename extension of ".h", ".cc",
or ".tcc", so those were the files I scanned.  It turns out that 
there were already files in the library in violation of the policy, 
so I missed scanning those.  They might or might not have bad 
static local initializations.

Under what seems to be becoming the new policy to avoid labeling 
headers with standard extensions (for no more sound reason than vague 
inclination, AFAICT) I don't know how I would construct the "find" 
command to repeat such a scan.  

Given the difficulty of identifying C++ sources without filename
extensions, I doubt I or anyone else will be doing much more auditing 
in libstdc++ under any such policy.

Nathan Myers
ncm at cantrip dot org