Try playing your modified golf game with a program to produce the 100 bottles of beer song. The winner is obvious, but I maintain is more complex from a maintainance perspective than a far shorter dynamic solution.
All forms of golf raise the question of trying to define what kind of shortness is appropriate. There is no good answer. And the more natural the answer that you try to come up with, the trickier the boundary cases become. There is no good solution.
PS Stupid trick for regular golf. If side-effects are unspecified, then eval is often more shortly written as s//print"Some code here"/e
-
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.
|
