the mug of Perl
in [Perl]
|
Prev: FAQ 8.37 How do I find out if I'm running interactively or not?
Next: FAQ 5.4 How can I use Perl's "-i" option from within a program?
From: John Bokma on 30 Mar 2010 15:34 Jürgen Exner <jurgenex(a)hotmail.com> writes: > John Bokma <john(a)castleamber.com> wrote: >>As for what I would put on a cheat sheet: >>http://johnbokma.com/perl/perl-quick-reference-card.html >> >>Note that it's outdated, and probably incomplete. I hope to have time >>soon to add the more recent stuff to it, and also add what is available >>since which version of Perl. > > I find it very interesting where you put the emphasis on your sheet: > 3 1/2 columns out of 5 deal with regular expressions, only 1 1/2 are > actually Perl itself.. :-). Note that there is more than one columm blank, and I am open to suggestions what to put there. > What I would include/add from my perspective: > - Perl functions by name sorted by category as in perldoc perlfunc but > with argument list and return value, including indication for optional > arguments Yes, I have been thinking about that. Or at least the Perl functions that set as a side effect $! or similar [1]. But (!) a function can be looked up using perldoc -f function. OTOH, Programming Perl's function reference is sometimes more clear regarding if $! is set or not. For example, perldoc -f chdir doesn't mention [2] that $! is set if false is returned, while PP's entry for chdir makes this clear with a boxed $! to the right of chdir and it has an example that shows this. On top of that the PP documentation also shows that chdir raises and exception if fed tainted data. > - Perl syntax, at least for less common constructs, e.g. modifiers > - syntax (maybe by examples) for references and OO There are several Perl cheat sheets out there that cover this information. references and OO in itself would be 2+ pages I am afraid. Especially if you want to include modern Perl stuff (Moose, etc.). [1] Like Programming Perl does with the small boxes to the right of the function name in the "Perl functions in alphabetical order" section. [2] explicitely I mean, it can be guessed from the context, though. -- John Bokma j3b Hacking & Hiking in Mexico - http://johnbokma.com/ http://castleamber.com/ - Perl & Python Development
From: Ben Morrow on 30 Mar 2010 16:31 Quoth John Bokma <john(a)castleamber.com>: > Jürgen Exner <jurgenex(a)hotmail.com> writes: > > > What I would include/add from my perspective: > > - Perl functions by name sorted by category as in perldoc perlfunc but > > with argument list and return value, including indication for optional > > arguments > > Yes, I have been thinking about that. Or at least the Perl functions > that set as a side effect $! or similar [1]. But (!) a function can be > looked up using perldoc -f function. OTOH, Programming Perl's function > reference is sometimes more clear regarding if $! is set or not. For > example, perldoc -f chdir doesn't mention [2] that $! is set if false is > returned, while PP's entry for chdir makes this clear with a boxed $! to > the right of chdir and it has an example that shows this. > > On top of that the PP documentation also shows that chdir raises and > exception if fed tainted data. This is the sort of thing that would make a perfect doc patch. Much of the documentation of basic functions like this dates from the days when you were expected to know that $! was errno, and check your local chdir(2) to see what it might be set to, and most of the porters probably don't read it often enough to notice where it hasn't been updated. Doc patches from people who actually read the docs because they don't know how things work yet are always the most valuable, and not always easy to come by. <snip> > [1] Like Programming Perl does with the small boxes to the right of the > function name in the "Perl functions in alphabetical order" section. If you felt like going through perlfunc and adding this sort of annotation to the entries I expect p5p would accept a patch. (I can't guarantee anything, of course, seeing as I don't have a commit bit.) Ben
From: Justin C on 30 Mar 2010 17:31 In article <f63f9acd-ed20-4442-a1f1-6b2cd6503179(a)8g2000yqz.googlegroups.com>, ccc31807 wrote: > http://nostarch.com/mugperl.htm > > cheat sheet is here: > > http://nostarch.com/mugperl_big.htm > > The cheat sheet appears to be targeted more to the casual user rather > than to the daily grind. I wondering what would appear on a cheat > sheet for journeymen Perlistas. My nomination would include the ||= > operator. 13 bucks for a mug? What kinda mug do you take me for?! Justin. -- Justin C, by the sea.
From: Dr.Ruud on 30 Mar 2010 19:37 John Bokma wrote: > http://johnbokma.com/perl/perl-quick-reference-card.html Another: http://juerd.nl/site.plp/perlcheat -- Ruud
From: Keith R. Watson on 31 Mar 2010 08:28
ccc31807 <cartercc(a)gmail.com> wrote in news:f63f9acd-ed20-4442-a1f1- 6b2cd6503179(a)8g2000yqz.googlegroups.com: > http://nostarch.com/mugperl.htm > > cheat sheet is here: > > http://nostarch.com/mugperl_big.htm > > The cheat sheet appears to be targeted more to the casual user rather > than to the daily grind. I wondering what would appear on a cheat > sheet for journeymen Perlistas. My nomination would include the ||= > operator. > > CC This one is rather good. Perl Reference Guide & Perl Pocket Reference http://www.vromans.org/johan/perlref.html At the bottom of the page is a link to the PDF version http://www.squirrel.nl/pub/perlref-5.004.1.pdf keith -- Keith R. Watson Georgia Institute of Technology Systems Support Specialist IV College of Computing keith.watson(a)cc.gatech.edu 801 Atlantic Drive NW (404) 385-7401 Atlanta, GA 30332-0280 |