Perl programs written in a style that is as close to C as possible are more easily understood by most other programmers.

Something like this?

undef $/;
my @text = split (//, <$FILE>);
for (my $i = 0; $i <= $#text; $i++) {
    my $j = $i;
    if (($text[$i++] == 'h' || $text[$i++] == 'H') && 
        $text[$i++] == 'e'...) {
        while ($j <= $i) {
            print $text[$j++];            
        }
    }    
}

[download]

I'll be the first that would recommend a solid foundation in programming, C or otherwise, but writing Perl as if it was C, isn't what would make your Perl better understood by other (Perl?) programmers.

Software speaks in tongues of man; I debug, therefore I code.
Stop saying 'script'. Stop saying 'line-noise'.

In reply to Re^2: Perl 'grammar' by Erez
in thread Perl 'grammar' by gortok

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.