You won't be able to give them a useful introduction to Perl in one hour.
But that's a good thing, because it frees up a whole hour for you to give them something much more valuable: an appreciation of the language.
Here's what I'd do, if I were giving your talk:
- Write a couple of scripts that they would find useful. Stuff that solves real problems they face everyday. They don't have to be huge problems...sometimes automating a repetitive niggle can be more valuable in terms of the cumulative time and frustration saved.
- Demonstrate those scripts. On real data. Or at least on plausible data.
- Then show them how some of the scripts work. Go through one or two of the scripts. Point out how "naturally" they read (and make sure they do read naturally!) Work through the copious and meaningful comments. Demonstrate the clever decomposition of the task into obvious and easily grasped subroutines.
- Suggest some resources in case they'd like to learn more. Books, the Perl documentation, Perl Monks, CPAN, etc. In particular, briefly show them some of the existing text-extraction and language-related modules on CPAN.
- Leave plenty of time for questions. Encourage the scholars to discuss the problems they need to solve, then outline (very generally) where and how Perl might help them solve those problems. If a particularly simple problem is put forward, solve it on the spot (and, if that idea appeals to you, don't hesitate to "plant" someone in the audience to propose a prearranged problem!)
Personally, I'd probably steer clear of all but the simplest regular expressions (e.g. nothing more complex than m/Mac[a-z]*/gi
) , since Perl 5 regex syntax is scary even to many experienced programmers.
And I guess if I were giving the talk, since they're presumably language scholars I'd probably finish off by showing them one of the scripts translated into Latin.
But that'd just be showing off, and certainly not necessary to the success of the presentation. ;-)
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||
Others about the Monastery:
(5)As of 2017-01-25 02:03 GMT