Your employer (or whoever) should consider relaxing to http://green-brick.foobar and http://foo.bar/green-brick. A hyphen is perfectly valid in a server name, and saves you a lot of trouble.
However, there are ways to do what you ask. Here's a very naive approach:
#!/usr/bin/perl -l
use strict;
use warnings;
# build word list in %words
my %words;
open my $dict, "/usr/dict/words";
chomp, $words{lc $_} = 1 while <$dict>; # UPDATE: added 'lc'
close $dict;
my $str = "perfumesmellslikecheese";
$str =~ m{
^ # anchor to beginning of string
(?{ [ ] }) # start $^R as an empty array ref
(?: # match this block <<
(\w{2,}) # capture 2 or more letters to $1
(?(?{ $words{lc $1} }) # if lowercase '$1' is in %words...
(?{ [ @{$^R}, $1 ] }) # add this word to the current list
| # otherwise...
(?!) # fail (force \w{2,} to backtrack)
)
)+ # >> one or more times
$ # anchor to end of string
(?{ print "@{$^R}" }) # print the words (with spaces)
(?!) # fail (cause everything to backtrack)
}x;
You can make the engine a great deal smarter by making it dynamically adjust -- making it only possible to match things you KNOW to be words, for example.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|