On 7/28/07, Bob Rogers <[EMAIL PROTECTED]> wrote: > 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? > Parrot::Distribution offers a number of subroutines which allow one to specify which subset of parrot files you wish to select for testing. this is built into the tests, and if everything is working as it should (and i believe it is,) it means that calling the proper function from this distribution will provide the proper subset of files (e.g. c_language_files.)
> 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. > received just fine :)
