split looks like a better choice than a regex. I whittled away at this and came up with the untested:
for (split(/:/, $$pattern)) {
# make sure it starts and ends with spaces
$_ = 'S0' . $_ unless /^S/;
$_ .= 'S0' unless /S\d+$/;
my @pieces = split(/[SF](\d+)/, $_);
while (my ($spaces, $fills) = splice(@pieces, 0, 2)) {
$out .= " " x $spaces .
substr($camel, $camelcount, $fills);
}
$out .= "\n";
}
I'm fairly pleased with that, but might try to fit a
pack in there. (How would you have used
map?)
Aside, this:
while (/(.)/g) {
$camel .= $1 if $1 ne " ";
}
could be spelled:
tr/ //d;
$camel .= $_;
I'm sure you can trim that down more, too. Don't forget to check out
Acme::EyeDrops for a different take on things.
Update, very shortly after: You could, of course, just split on [SF] and probably get the same effect, though you'll have an empty element at the start. It may or may not be more clear that way.
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.