On 17/03/10 19:50, Eric Blake wrote: > On 03/17/2010 11:30 AM, Jim Meyering wrote: >> Filtering out lines ending in \n\ >> and the few remaining false positives wasn't too bad. >> I've just fixed everything reported by this: >> >> $ for c in *.c; do cpp -fpreprocessed $c 2>/dev/null \ >> | grep '[a-zA-Z0-9](' \ >> | grep -vE '(\\n\\$|%s\(to >> %s|delimit-method|(date|group|character)\(s\))' \ >> | grep . && echo "*******$c*******"; done
Cool. Note -fpreprocessed was not in gcc 2.95.3 but was in 3.0.4. >> >> I'll repost when I've massaged the above into a syntax-check rule. > > That would be a nice syntax-check rule to push upstream into gnulib (of > course, projects with other notions of formatting style, like libvirt, > would have to update cfg.mk to avoid that rule). Seems a bit specific for inclusion in gnulib IMHO. Something more general like sparse would be better there I think. cheers, Pádraig.