re consideration: I am strongly against changing the title. This title was chosen because it most concisely states the point: the cheat sheet as a perldoc, under the name perlcheat. This title was very carefully chosen, years ago. Vote as you wish, and change the title if you must, but you should at least know my opinion.

Update (20030812)
perlcheat was accepted and will very probably be part of perl-5.8.1.

A few months ago, I posted my Perl Cheat Sheet here, and today it's at its seventh version. I'm only updating the one on my website, because I'm too lazy to copy and paste it every time. But neither the new version nor me being lazy is the reason for posting another meditation.

Some people suggested to me that it I should ask if the cheat sheet should be included in the Perl documentation as perlcheat. I'm not sure though. It's worth the try, but before I try, I'd like to know what you think.

I'd like to thank everyone who e-mailed or messaged me about this thing. And of course all people who link to it and all people who upvoted the node; it's the most popular Perl-related page on my website, and it's my best node (reputation-wise) ever.

Juerd-
I like Cheat sheets. They help with the everyday stuff until it become routine. I would submitt the idea, any good SW book has a summery of commands in the appendix. Worst case let them say no and keep the page up for those in need.

One comment on your Cheat Sheet. It would be nice if you did something in addition to making the titles Bold to make them stand out. Maybe Underline too.

I think it looks great, hadn't seen it before. A lot of useful information in a small space. I vote for including it as it would be handy to just be able to say perldoc perlcheat whenever I wanted to see it again.

I like cheatsheets. A lot. For one reason or another, I have a lousy memory, and often need a quick refresh to key into the knowledge that has been lost somewhere in my brain. For this reason, I have a large list of aliases in my .tcshrc file, and I am never without my PDA.

As a matter of fact, I don't think "cheatsheet" is a fair name. As long as you're not taking a closed-book test, who cares if you need a quick refresh on pack? Isn't that what documentation is for in the first place?

Adding a cheatsheet to perl would be a godsend. We've already got perldoc. Why not include a quickie version? It's not like we're adding a 100 meg PDF to the binary. For what it's worth, I say go for it, and I'll look forward to seeing perlcheat in Perl 6.

The next version of Perl will not be Perl 6, and this cheat sheet is a Perl 5 cheat sheet.

Perl 6 is a new language. Most of this cheat sheet does not apply to Perl 6. Heck, most of Perl as we know it does not apply to Perl 6. I think the difference between Perl 5 and 6 will much greater than the difference between C and C++ :)

I like the cheat sheet. As far as adding it to the
distribution, I think it is a good idea. I think a
better name for it is 'quick reference guide'.

I was unable to get a clean text
formatted version of the sheet from your web site.
Cut-and-paste brought weird characters in, and the 'view
source' version has escaped characters.

For content, I would like more about
exists, defined, keys, values,
and ref.

For typography, I think a PDF would be a great addition!
A PDF could hold more information. I would like a
PDF that could be rendered into a little
four-page booklet, created by folding a double-sided
printout.
Those of us without young eyes could print on two
double-sided sheets, or use bigger paper.
A narrow version suitable for taping to the
side of a monitor would be a true 'cheat sheet'.

A PDF version with various page layouts would
make a great addition to the test suite of
the PDF generation modules.

No, there's no room for a very long URL like that. The only URLs that are unimportant enough to go are tpj.com and perldoc.com, both too short to be replaced with perldoc.perl.org. It should be perl.org/doc or doc.perl.org anyway, and not have "perl" twice in the URL. (The reason for using perldoc in full was Google ranking. I don't agree with optimizing for search engines either.)

It should be perl.org/doc or doc.perl.org anyway, and not have "perl" twice in the URL.

Does it also bother you that every perldoc about perl has perl in it's name? For example, perlreftut, perlfunc, perlsec... That is to say, that the perldoc already says that we're looking at the documentation for perl, why prefix the subject with perl again?

thor

Feel the white light, the light within
Be your own disciple, fan the sparks of will
For all of us waiting, your kingdom will come