I agree about the CPAN thing.

Perl's a programming language. They've seen programming languages before, they'll see them again.

But I bet they have no idea how enormous CPAN is and all the weird and wonderful stuff that's in it.

Taking something like Lingua::EN::Sentence for instance.

Throw this question out to the class --

What's a sentence? Anything up to a full stop? Nope, not good enough. Anything up to a full stop followed by a space? 

Maybe ... maybe not.
        ^^

[download]
OK then, full stop, space, uppercase letter? I'll ask 
Mr. Jones
  ^^^

[download]
if he thinks that's smart enough an algorithm. He works for 
I.B.M. I think.
     ^^^

[download]

"Wow, that's a lot harder than it looks."

Oh yes and we forgot about quotes, question marks and exclamations.

The point of all this being that someone has sat down and thought really hard about all those things for a really long time and come up with Lingua::EN::Sentence so they don't have to. Plus of course it's easily extensible in case they find something it doesn't catch. 

use Lingua::EN::Sentence qw( get_sentences );

$text = "
I agree about the CPAN thing. Perl's a programming language. They've
seen programming languages before, they'll see them again.
But I bet they have no idea how enormous CPAN is and all the weird
and wonderful stuff that's in it. Taking something like
Lingua::EN::Sentence for instance. What's a sentence? Anything 
up to a full stop? Nope, not good enough. Anything up to a full stop 
followed by a space? Maybe ... maybe not. OK then, full
 stop, space, uppercase letter? I'll ask Mr. Jones if he
  thinks that's smart enough an algorithm. He works 
for I.B.M. I think. \"Wow, that's a lot harder than it 
looks.\" Oh yes and we forgot about
quotes, questionmarks and exclamations!";

my $sentences = get_sentences($text);    ## Get the sentences.
foreach my $sentence (@$sentences) {
    print 'SENTENCE: ', $sentence, $/;
}

[download]

($_='kkvvttuu bbooppuuiiffss qqffssmm iibbddllffss')
=~y~b-v~a-z~s; print

In reply to Re^2: strange responses to inhouse perl training by Cody Pendant
in thread strange responses to inhouse perl training by jim_neophyte

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.