comment on

🏌 ⛳

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:

The Lighter Side of Perl Culture (Part IV): Golf

The Decline and Fall of the Roman Empire by grinder (2005) - Roman Numeral obfu (see especially ambrus reply)
(Golf) Let's go bowling by virtualsue (2001) - many replies

Some Perl Monk Golfers

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

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.


Clear questions and runnable code get the best and fastest answer
	PerlMonks