From: "Paul Cochrane" <[EMAIL PROTECTED]>
Date: Sat, 28 Jul 2007 13:39:09 +0200
. . .
A longer term strategy would be to check for recently changed files
(since the developer's last "svn up") and to run the coding standards
tests only over those files . . .
Paul
As a step in that direction, is there an easy way to find out which
coding standards tests should be applied to a given source file? Some
have "c_*" names, which makes it seem pretty obvious . . . until you
consider *.pmc and *.ops files, which are "sorta C."
I am asking because I just sat down to write a
M-x parrot-check-coding-standards command for Emacs, but realized that I
didn't know which tests to run. I could read the test code and hardwire
a mapping, but that would be wicked fragile. Is a naming convention
sufficient, or would we need a metacomment in the test file?
TIA,
-- Bob Rogers
http://rgrjr.dyndns.org/
P.S. I have been having problems with getting parrot-porters to accept
my posts, so I don't expect this to appear on the list.
