No need for piping through perltidy, Perl::Tidy with the right config can do the trick.
Update:
#!/usr/bin/perl
use strict;
use warnings;
use Perl::Tidy;
my $input = <<'_EOT';
sub Tidy {
my ( $text, $cmdopt ) = @_;
my $tmpfile = "/tmp/Tidy.$$." . join( '', localtime()) ."tmp";
open my $th, ">$tmpfile" or die;
print $th $text or die;
close $th or die;
my $pid = open my $ph, "perltidy -st $cmdopt $tmpfile |" or die;
my $tidied = join '', <$ph>;
close $ph or die;
waitpid $pid, 0;
unlink $tmpfile;
return $tidied;
}
_EOT
my $output;
Perl::Tidy::perltidy(
source => \$input,
destination => \$output,
);
print $output;
-
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.
|