|
I was born. That's all I remember.
sauoq.perlmonk.org | My scratchpad
The True Catacombs of Perlmonks | What XML generators are currently available on PerlMonks? | Perlmonks Related Scripts | Friar | Writeup Formatting Tips | PerlMonks CSS Examples | Chatterbox Stats (external)
The editors' hall of mirrors and trickery
Little Nuggets of Good Advice:
- Don't use prototypes until you fully understand the issues in Tom Christiansen's article about them.
- Don't get preoccupied with performance; your time is more valuable than the machine's.
- Don't use indirect object notation.
Perl Annoyances (yeah, it has a few.)
- if (%hash) { ... } won't work as expected with a tied hash.
- There is no easy way to reliably determine whether a reference is a reblessed qr//
- Two argument open is used with <> (and subsequently with -p and -n) resulting in potential security issues.
- You need no warnings 'qw'; to do qw/ # / quietly.
- sub x { 1 for 1 } returns !1 instead of 1 like you might expect.
- Requiring values or keys to reset the each iterator is ridiculous. In fact, each sucks in general.
Some Insteresting Nodes
The wonderful series, Meditations on Programming Theory, by mstone:
A selection of posts on XP and reputation:
Killer Obfu:
Miscellaneous interesting nodes I have yet to categorize:
Perl Weirdness!
Info about PM related third-party websites.
Some chuckles...
Monks whose homenodes I find interesting for one reason or another:
Things of Mine
- Don't Retitle This Node (See also: Consider this: What makes a good node title? and my note below.)
- Abstain option? (I'd still like one.)
- Re: When to -- (This is how I vote.)
- Re: Creating bash functions using perls $ENV interface
- Re: Randomize lines with limited memory
- Re: Ksh
- But... SimpleTemplate really is.
- Re: What should be returned in scalar context? (best practice)
- When the Best Solution Isn't
Useful Stuff
One-liners
Hex viewer: perl -0777e'$i++,print $_.($i%20?" ":"\n")for unpack"(H2)*",<>;print"\n"' file
Useless Stuff
Finally, some japhs I can call my own
Another variation on the theme:perl -e "s();echo Just another Perl hacker,|;;open _;print<_>" perl -pe "BEGIN{@ARGV='echo Just another Perl hacker,|'}"
And another. this one only works on *nix, I'm afraid.perl -pe "BEGIN{@ARGV='perl -le print+q~Just\ another\ Perl\ Hacker,~| +'}"
The windows version isn't as nice. (I much prefer the -i\| in the *nix version.):perl -i\|perl -le 's//$^I -e"print q-Just another Perl hacker,-"/;open + _;'
perl -i"|perl" -le "s//$^I -e\"print q-Just another Perl hacker,-\"/;o +pen _;"
Some Opinions
On Node Retitling
This summary is taken from a reply to Tanktalus somewhere under Consider this: What makes a good node title?:
The best titles are not the ones you think are best. In fact, the whole concept of best in this instance is a local optimization and a function of the searcher. Retitling nodes in an effort to bring them closer to our preconceived notions of what makes an ideal title is necessarily introducing inefficiency. Good search coverage is, essentially, an emergent phenomenon. The assumption that we can help it along by retitling nodes is fallacious.
A lot of • ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••