I wouldn't assume that about Damian's module. Damian writes really cool string processing, but he usually uses algorithms that do a lot of recopying. That can lead to excessive memory use, particularly on long strings.
So if you need efficiency, you probably need to roll yor own or use someone else's. Everyone is saying to use while, but nobody gave you sample code. Let me rectify that with a simple script that should run fairly efficiently:
#! /usr/bin/perl -w
use strict;
use HTML::Entities qw(encode_entities);
my @stack;
while (<>) {
while (/\G([^{}]+)|\G([{}])/g) {
if (length($1)) {
print encode_entities($1);
}
elsif ("{" eq $2) {
my $pos = pos($_);
if (/\G(\w+)/g) {
print "<$1>";
push @stack, $1;
}
else {
die "Unnamed opening brace at character $pos, line $.";
}
}
elsif (@stack) {
my $tag = pop(@stack);
print "</$tag>";
}
else {
my $pos = pos($_);
die "Unmatched closing brace at character $pos, line $.";
}
}
}
if (@stack) {
die "Unclosed tags at end of file: '@stack'";
}
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.