I guess I was trying to say that I don't think that permitting cut'n'paste is itself the motivating factor for the change. I got the impression from Damian's comments that it's about reducing one factor that might daunt (does daunt?) Veebians, Javanese, etc. when trying to use Perl, by giving in to the common convention.

Also, now that I think about it, I don't think there's anything wrong with using example code, and I don't think that's the same as cargo cult. Everyone does it from time to time (raise your hand if you own the Cookbook) especially when starting out on a new topic. The question is, will you stop with that? Will you let the example persist unmodified into production, without bothering to figure out what it's doing?

I think this is mostly a matter who you are - whether you've got the drive to understand, and take pride in your work. I think it was Socrates who said "The unexamined code is not worth executing", but there are plenty of people who wouldn't properly examine their code no matter what language they're using. Making conversion of VB code into Perl easier, by itself, IMHO, won't encourage cargo cult any more than the Cookbook does now.

-- Frag.

In reply to Re: Re: How I Learned to Stop Worrying and Tolerate the Dot by frag
in thread Dots and cargo-cult programming by bikeNomad

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.