tallulah, your current answer does the job pretty well.
You should certainly break out "checkForLetters" as a subroutine, and pass in the sentence and the wanted letters.
That would make it easier to test your code, which is always a plus.
You could replace your for(;;) loop with a foreach(@a), which might make things a bit more readable.
But apart from that, I don't see any major improvements. You could do the whole thing as one grep statement, but I don't think that would add any clarity.
Edit: In the TMTOWTDI spirit, here's an (almost, except for the split) regex-free implementation:
sub checkForLetters {
my ($sentence, $wantedLetters)=@_;
# don't need this variable (or any of them, in
# fact -- they're just here for clarity.
# we could work straight out of @_ if we wanted
# this terser
# Also, the $[ check is just pedantic - if someone
# changes $[, shoot them.
my $foundLetters=scalar (grep index($sentence,$_)>=$[,
split //,$wantedLetters);
return length($wantedLetters)==$foundLetters;
}
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.