[Box Backup-dev] Merges

[E.W. Peter Jalajas]

One tiny development-side thing that I could contribute to the project,
until the compiler --enforce-coding-stds option is created, that I've
always wanted to do and had a minor passion about, is to write scripts
that scan the entire source code tree for various issues, including
common security holes (for example, buffer overflows; un-validated
input strings), coding standards, copyright/license strings, string
capitalization, etc.  

At first, this script could be run manually periodically locally on my
computer and I'll report the issues found to the -dev list, but then if
it proves worthy, it could maybe be added to the check-in validation
process at some level between simple reporting and heavy-handed
enforcement.  At first it would have to be optional, lest nothing would
get checked in any more :-).

At first, it could just report issues; maybe later it could maybe
correct simple issues (for example, replace tabs with spaces, or
replace copyright 2001 with Copyright $CurrentYear). 

I tend to write things like this for my own use in shell (bash, and
less frequently now ksh), but I wouldn't have a problem coding it in
perl if preferred.

Any interest in such a beast?  Is there such a thing out there already?

Pete
--- Chris Wilson <chris at qwirx.com> wrote:

> Hi Ben,
> 
> On Sun, 20 Aug 2006, Ben Summers wrote:
> 
> > I hope everyone else thinks coding standards are important.

> > I read a essay recently which suggested that the compilers should 
> > enforce coding standards. 
> I think it would be a good idea, but it would have to be optional, or
> else 
> nothing would compile any more :-)