OK, I see where you are going with this.

I guess part of my problem is that I've been discussing this inside the wrong frame. And like you said, conflating OO, code generation, and so on isn't going to help.

I'd be fine with writing procedural code using functional techniques, 1st class functions, closures, etc.

That may end up off limits. :(

FWIW, there was a Java guy on our team who honestly thought that the map function resulted in unmaintainable code. In any case, Point Guy thinks that once Perl finishes building a parse tree, it's done compiling. That hasn't been my understanding for years and years.

In reply to Re^2: Help me avoid writing C Programs in Perl for a living by cleverett
in thread Help me avoid writing C Programs in Perl for a living by cleverett

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.