Like I said before, figuring out when to use parens is the tricky part. :) MeowChow pointed out that my solution didn't account for operators which aren't associative ("2 3 4 + -" should be "2 - (3 + 4)" instead of "2 - 3 + 4"). Then I noted that this information was missing from the data provided in the original problem.
I decided to tackle the problem of associativity, and came up with this solution, at 171 characters in the body of the sub:
%o = ('+' => 1,
'-' => 1,
'*' => 2,
'/' => 2,
);
%a = ('-' => 1,
'/' => 1,
);
sub rpn2ltr {
for$i(@r=@_){if($p=$o{$i}){$r=$p>($r=pop)->[0]||($p==$r->
[0]&&$a{$i})?"($r->[1])":$r->[1];$l=$p>($l=pop)->[0]?"($l->[
1])":$l->[1]}push@_,[$p||9,$p?"$l $i $r":$i]}$_[-1][1]
}
It's pretty ugly. :/ I hope someone will provide a more elegant solution!
-
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.
|