I have to say that spell checking code seems a little unlikely to me. It assumes a pretty stringent and specific set of rules about writing code and what I would consider to be a stupendous conformance to that set of rules. I seldom spell thing correctly when making variable for example. A typical variable I might use would be %qs_m which to me means "hash of query strings of type that return multiple values".
I can understand the need for coding standards, really, I do! But when it gets down to it, I will occasionally provide a map or dictionary to explain variables (Or anything else in the code) if it seems needed. The level of standardization that would require spell checking my variable names and method calls would so much hinder my coding process! No matter what, if I have to look at someone else's code, the best way to figure out what is going on is to fire up a debugger and step through it. Simply reading it, regardless of how it is standardized, does not help me one bit.
Seems to me that is what POD is for.... .
I wish I knew of a tool to help out, but honestly, I can't imagine the ROI on such a tool.
To be clear, this is my opinion and not a criticism!
If I am way off, don't hesitate to tell me about it. I would honestly like to understand the value of that level of code checking...
- ...the majority is always wrong, and always the last to know about it...
- ..by my will, and by will alone.. I set my mind in motion
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.