🏌 ⛳

Curiously, in addition to code golf, I've enjoyed a life long passion for real, physical golf. Though I can't compete with Tiger Woods (either on or off the golf course), my golf was once strong enough to represent my club in pennant matches. I fondly remember competing against other clubs in the good ol' days, especially punching the air with my fist while eyeballing my match play opponent after holing a crucial putt from the edge of the green. Though unable to physically eyeball my code golf opponents nowadays, I do frequently indulge in Tiger-esque fist pumps while code golfing at my desk, sometimes even leaping out of my chair to do so.

-- from The golf course looks great, my swing feels good, I like my chances (Part VI)

Not specifically answering your question, but you seem to have become addicted to the competitive aspect of code golf. Though currently retired, I've experienced first-hand how addictive it can become, how you find yourself shaking your fist in fury at someone you don't know, from the other side of the world, who just had the temerity to pass you on the code golf leaderboard! :)

BTW, tybalt89, who answered your post with the 44 character solution, is mentioned in some of the links below and is one of the all-time golfing greats, and yes he is on the other side of the world to me, and yes he used to regularly pass me on the Perl golf leaderboard ... though I didn't shake my fist in fury at him because I knew how good he was and expected it; I shook my fist most often at `/anick, who I expected to beat, but sometimes didn't.

If you are eager to improve your golfing skills (as opposed to getting others to solve the problem for you) you could learn from the vast amount of prior art in code golf, for example by reading and understanding the many solutions described in the code golf nodes below:

Some Perl Monk Golfers

See Also

Many references were added long after the original reply was made

In reply to Re: reduce code (Golfing References) by eyepopslikeamosquito
in thread Golf code in perl by tt08

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.