| Paul Scott 2007-05-16, 4:03 am |
|
On Wed, 2007-05-16 at 16:03 +1000, Greg Sherwood wrote:
> Either way, you'll need to create your own coding standard directory and
> a coding standard class (check the docs for a tutorial). In your coding
> standard class, you'll want to define a list of sniffs that your new
> standard includes.
I have already created a new standard and most of it is working just
fine. Just this little problem is getting me down at the moment.
I will take another look at it today and see what I can do with
manipulating the FileCommentSniff that I already have, and let you know
what is happening.
On another note, I will be deploying this stuff as a web service at some
stage, and could easily use the existing standards as well if anyone has
an interest in that. Please let me know, and or email me your standards
if you would like to have them included; that way, we could build up a
decent service that a whole lot of people could use without the hassle
of creating a standard for themselves without polluting PEAR with a
zillion similar standards.
--Paul
|