Re: Re: PHP_CodeSniffer: Patchlevel updates break our Coding Standards

Christian Weiske <[email protected]>
Newsgroups gmane.comp.php.pear.general
Message-ID <20130228074413.427beb4f@bogo>
Hello Greg,



> It seem you have misunderstood the purpose of the generic sniffs. The
> way to use them is to cherry pick the ones you want; not to include
> the whole bucket of sniffs and then exclude the ones you don't. They
> are unrelated, and many conflict with each other. So I suggest you
> swap around to this model and you wont have any problems with the
> code I release as you will be in full control of your standard.

Thanks for the hint, I wasn't aware that the generic sniff shouldn't be
used the other way round. My rant is pointless then.

> I think I'm doing a pretty good job in this area and find your email
> quite insulting.
Let me tell you that I'm sorry for that. The next time I think
something is seriously wrong with anyone's actions I'll first contact
him in private.

My reason for sending the mail to pear-general is that I'm used to
discuss things in public, especially with PEAR. As you noted, that
wasn't the right place for a rant.

-- 
Regards/Mit freundlichen Grüßen
Christian Weiske

-=≡ Geeking around in the name of science since 1982 ≡=-
signature.asc (application/pgp-signature, 198 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAlEu/L0ACgkQFMhaCCTq+CNbLgCg2u83UR8CtMOWENkAdIPRJKsA
SZcAnRJutWQPn3BznSG1N8425L/uFyOG
=KuCH
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.