Refactoring can be pure fun. It can also be helpful for learning or reorganizing and making things easier to maintain. Maybe it's time to bite off a bigger piece and do more of your stuff in a template as recently revisited. :P
#!/usr/bin/env perl
use utf8;
use 5.14.2; # for s///r
use strictures;
use Template;
use Path::Tiny;
# Mocking… you'd replace with your actual routine.
sub Path::Tiny::textify { # Monkey patch.
my $self = shift;
join " ",
map ucfirst,
split /[\W_]/, $self->basename =~ s/(?<=\w)\.\w{1,3}\z//r;
}
my $tt2 = Template->new;
my @files = grep $_->is_file,
path(".")->children( qr/\A[A-Z].+/i ); # Should probably have \z t
+oo.
$tt2->process(\*DATA, { files => \@files })
or warn $Template::ERROR;
__DATA__
<ul>
[%-FOR file IN files %]
<li>
<a href="./[% file.basename | uri %]">[% file.textify | html %]<
+/a>
</li>
[%-END %]
</ul>
<ul>
<li>
<a href="./WADO-OsiriX-notes.txt">WADO OsiriX Notes</a>
</li>
<li>
<a href="./chinese-truncate.pl">Chinese Truncate</a>
</li>
<li>
<a href="./Dockerfile">Dockerfile</a>
</li>
…etc…
</ul>
-
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.
|