Re^2: Perl influences?

Replies are listed 'Best First'.
Re^3: Perl influences? by eyepopslikeamosquito (Archbishop) on May 05, 2005 at 21:51 UTC
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.	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^3: Perl influences?
by eyepopslikeamosquito (Archbishop) on May 05, 2005 at 21:51 UTC

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.