With the onslaught of golf meditations recently (of which I shall soon be posting one -- fear not!), I'm posting a set of reminders that you may be wont to take heed of, ere you post again!
- if you use a regex, be sure . can match a newline, by using the /s modifier to the regex
- pop is two characters less than shift
- assign to @_ and $_ if you can -- it saves a my declaration (if you're stingy), and allows operations like regexes and pop to work without an argument
- screw $1 and the like, and use $& and its friends instead
- map() is probably a useful tool to master for golf
- leave out semicolons wherever possible
- don't explicitly return unless you must
- doing .$/ is shorter than ."\n" -- same for .$" vs. ." "
- {...;redo} is shorter than while(1){...}
- {...;$x&&redo} is shorter than while($x){...}
- use || and &&
japhy --
Perl and Regex Hacker
-
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.
|
