I was most surprised to notice -- as pointed out in The golf course looks great, my swing feels good, I like my chances (Part IV) in the
"Which Language Produced the Shortest codegolf Code?" section -- that
the shortest Perl solution in the 1000 Digits of Pi codegolf game of 102 strokes
was far behind both Ruby (54 strokes) and Python (62 strokes).
This is unusual in the extreme because in the other 26 games Perl was consistently
well ahead of Python, yet here was 40 strokes behind! Why?
I'm afraid I don't know because I didn't play that game ... though I bet
"primo" does since he holds the lowest score in all four languages. :)
A wild guess is that Python has native bignums and that is crucial for this game.
The code golf forum for this game
may provide some useful tips. In particular, the Rabinowitz method
was recommended by "hendrik" (see for example this page) -- and hendrik solved this problem
in Python in 67 strokes, just five behind the Python leading pack.
Also, "hallvabo" suggested (if your solution is "close" to the 4 second time limit) submitting your
solution at different times of day because the codegolf server load apparently
varies considerably and your solution only need pass once to be accepted.
-
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.
|