comment on

I'm sure we've all heard the old "write-only language" attack on Perl, but I thought his rational was mildly interesting:

the language is so fantastically huge, no two programmers even appear to be writing in the same language

He's absolutely right that divergence in programming dialect between programmers is one of the biggest problems in maintaining large bodies of code. However, I don't agree that the size of the language has anything to do with the problem. C code written by two different people can be just as radically different as Perl code, and C is small language.

The only way to guarantee that Perl code on a large project is "read-write" and not "write-only" is the same as with any other language - coding standards and code reviews to make sure they're being applied. Nothing else will ensure that a group of programmers is coding in the same dialect.

-sam

In reply to Re: Perl for big projects by samtregar
in thread Perl for big projects by CountZero

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


P is for Practical
	PerlMonks