You could apply strong dictatorship on the perl files and say that they must pass a parser that checks the code for the proper things. A standards parser then it might work!

This is exactly one of the things I was trying to get at with my last node. I would like to check a huge pile of code, spread across multiple dirs, users, etc... and format them all corectly, document them in pod, convert the pod into an html api listing, check for inconsistancies in the api ( check code calls to functions against the included module's qw ( api_function1 ) statements and finally, check the code into cvs.

It seems like that's quite a tall order.

We are also trying to scale perl up to a size that it probably doesn't naturally fit into. TMTOWTDI probably means that the way you decide to do it may be completely foreign to your fellow developers, any kind of standards checker/parser, or even yourself in a few months ;-) However, a small team of people fluent in conversational Perl will be able to write the code that a company needs faster than a fleet of "baby talkers". Trouble is that in this job market, all most companies can seem to hire/retain are the less fluent, translation dictionary toting, "just visiting for the money" computer science tourists. It's reassuring to hear that other people are in the same situation, but I don't hear that many success stories. That's quite discouraging.

I hope this post doesn't come off as a rant because I don't mean for it to be so... I would like to see problems like these affect a change in Perl rather than result in a lot of complaining and hot air. We are going to try to make it happen in our company... If we can't we'll be forced to move some code to other, stricter, languages

-pos

The truth is more important than the facts.
-Frank Lloyd Wright

In reply to RE: RE: why i may have to leave perl... by pos
in thread why i may have to leave perl... by eduardo

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.