Just to fill in the background a bit... our discussion, or at least my part of it, centered entirely around the word "violation." A style "violation" assumes some sort of accepted coding standard and there can be no violation in the absence of one.¹ Even a "community style guide" would not resolve the issue as one would have to accept that guide before we could say he had any "style violations"

I agree with dragonchild's assessment of the PerlMUD code, by the way. I'd just label it "exceedingly poor style" rather than make claims about "violations". Perhaps I have an issue with authority. :-)

In any case, I do believe there are certain de-facto standards that exist for Perl code among those who aren't writing Perl in a vacuum. This has come up here before. (I'll post a node link here later. later: Here it is: My coding guidelines. Those are Abigail-II's coding guidelines, btw. Not mine.) And Best Practices seems to address this pretty head-on. For those who use it, Perltidy addresses at least some style issues in a more hands-on way.

[1] I make one exception: inconsistency is always a style violation. If it isn't consistent, it isn't a "style" at all.

-sauoq
"My two cents aren't worth a dime.";