More stuff derived from sh:
- # as comment character.
- Here-docs (perl's being much more powerful).
- Capturing command stdout with backticks, i.e. `$cmd`.
- "$var" interpolates $var, while '$var' does not.
- Built-in vars: $? status of last command; $$ pid; $0 program name.
- Having separate "string" versus "numeric" operators, albeit with different names; for example, shell uses = for string equality, -eq for numeric, while perl is more logical (string variants alphabetic), == for numeric, eq for string.
- && and || operators (ok, C has these too).
- the tr function seems inspired by Unix tr command, with y synonym to appease sed fanatics (modern day golfers being grateful for said sed fanatics early influence:-).
- Many other perl internal functions seem inspired from sh or Unix commands, for example: shift, chown, chmod, mkdir, eval, exit, kill, sleep, umask.
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>
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
Want more info? How to link or
or How to display code and escape characters
are good places to start.