Anyway, if I were to put manual page snippets on a Perl mug, my vote would go for another mini-language: the pack/unpack templates.

But if I was asked to design a Perl mug, I'd include an onion and a white circle with a red edge, the word "Java" in the circle, and a red line through the circle. (aka "No Java"). (Not that I want to pick on Java, but that's the most well known language with a coffee theme).

I must admit that at work I use Java mug (happy 5th birthday), but strictly for tea. Coffee goes into my Sybase mug.

Regarding \Z and \z. Now added. Thankyou for your suggestion.

I didn't think about pack/unpack but that's because it's something I so rarely use. It's also less likely to have appeal to the Java, Python and PHP members of the conference audience, whereas (so far as I know) Perl's regular expression syntax ought to be useful to all of those members.

A "No Java" message might get me into trouble, all things considered. ;)

Thanks again for your suggestion.

jarich

I didn't think about pack/unpack but that's because it's something I so rarely use.

That's exactly why I'd put it on a mug. Regular expressions is what people use all the time, and so they'll know most, if not all, of the syntax already. And since Perl regular expressions are firmly based on Henry Spencer's library, a lot of non-Perl users will not have problems with Perl regular expressions.

OTOH, I don't use pack and unpack that often. That's why I need to look up its syntax when I do use it.

Perl --((8:>*

In that same vein (or in the vein where I have my coffee injected)...

The things for which I'm always going back to "perldoc perlre" are:

(?=) positive look-ahead
(?!) negative look-ahead
(?<=) positive look-behind
(?<!) negative look-behind
[download]

In fact, I had to look them up again just now, to make sure I posted them right. (Having done this, maybe I'll be able to use them from memory next time.) These really are tremendously useful, and it would be swell to have them visible on my desk at all times (except when I'm drinking my coffee, of course).

I'm reluctant to suggest removing anything you have already, and I suppose you'd need to shrink the font if possible (and abbreviate "positive" and "negative") to make more stuff fit. If that were doable, and you ended up with enough room for just a couple more things besides "[pn].* look-.*d", you could add:

\p{...}  unicode class ...
[:...:]  posix class ...
[download]

(not much detail there, admittedly, but just getting the terms "unicode" and "posix" onto the mug seems worthwhile).

do{ local $/ = undef; <> }
[download]

T.I.M.T.O.W.T.D.I

h  s o h n a  o o t
e    r a e y     
r    e n          
e
[download]

The art is chosing the right one for your application.

The science is knowing which and why.

or one of dragonchild's old sigs

Perl + CPAN: 90% of every application is already written.

Let us show you how.

OK, I give up. What does the second one (i.e.,

h  s o h n a  o o t
e    r a e y     
r    e n          
e
[download]

signify?

I guess I should add a suggestion, too. I'd either use another CPAN-related quote:

CPAN is my programming language of choice.
The rest is just syntax.

or something simple and to-the-point:

#! /usr/bin/perl
use coffee;
[download]

In a pinch, a blown-down version of something from Obfuscation may be nice, although more illegible, like Camel code.

Do not rebuke them with harsh words ... but rather lead them gently - with URLs - so that they may learn wisdom.

The 'second' one is just a continuation of the first. Everything above the first horizontal rule is one suggestion.

The small letters are the vertical expansion of TIMTOWTDI. T(here) I(s) M(ore) ...etc. The two 'taglines' are also a part of that suggestion.

---

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

Or even more to-the-point:

#!/usr/bin/perl
require Coffee;

BCE
--Your punctuation skills are insufficient!

I like TMTOWTDI on a mug because the 'D' can stand for 'Drink'!

Chris
M-x auto-bs-mode

s/empty/coffee/mug;

was valid syntax.

That said, something that disproves perls reputation for being write-only is a good start.

There's always: $mug =~ s/^$/coffee/; ;-) Although it would be more like: $mug =~ s/^$/tea/ for me, personally ;-)

Hmmm, that would mean if there's a bit of cold coffee from yesterday, you're stuck - you aren't getting fresh coffee.

    $mug =~ s/.*/coffee/s, sleep(1500 + rand 600) while 1;
[download]

Or maybe:

    $mug =~ s/.*/beer/s, sleep(1500 + rand 600) while 1;
[download]

Perl --((8:>*

$mug->consume
   while $mug->is_not_empty;
[download]

-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.

And more importantly:

$mug->refill( $name_your_poison )
    if $mug->is_empty;
[download]

If only

s/empty/coffee/mug;
[download]

was valid syntax.

I just stumbled upon this, 8 years after it was written. Now the syntax is valid:

$ perl -Mstrict -Mwarnings -E '$_ = "empty"; s/empty/coffee/mug; say'
coffee
[download]

[In fact, as far as I can tell, it has been valid since 5.14]

-- Ken

I've had a good look at Juerd's Perl cheat sheet, erudil's regex quick reference and a few other similar documents. There's no way I can put all of any of those onto a itty bitty "can" mug. So what should I include?

With a lack coffee (ironically enough), this is the best coffee mug graphic I can muster at the moment. So I figured the least I could do was refill it. Unfortunantly the '~' only gets me half-full. And yes, dependent upon my mood, my coffee mug and beer mug look the same :)

I like the aesthetic zenness of this:

s/c[_]/c[~]/;
[download]

But this one actually works:

$_='c[_]';
s/\Qc[_]\E/c[~]/;
print $_,$/;
[download]

-jbWare

If it's a large enough mug (or my eyes were younger), Mark Lentczner's Periodic Table of the Operators might be amusing..

(Note that I am not Mark Lentczner, and I have neither met him nor correspondended with him)

use Perl;

It is Perlish, simple and elegant.

The three chief virtues of a programmer are: Laziness, Impatience and Hubris. — Larry Wall (Programming Perl)

Although perhaps that should be shortened to just laziness, impatience and hubris.

I'm shocked no one has suggested the canonical perl hack: Erudil's Camel Code. It's what came to mind instantly. Which may or may not be what you're looking for...

There’s Only One Obvious Way To Do It: use Perl!

I [red heart] P.E.R.L.

I think the most useful thing you could place on a mug would be

Have you tried "use warnings" or used "-w"?
Have you tried "use strict"?

:-)

A list of useful modules.

man perl
man perldoc
perldoc -f <functioname>
http://www.perlmonks.com
http://www.perl.org
http://www.cpan.org

"Be consistant. Be nice." -- Larry Wall

"Write for clarity first; let correctness follow naturally from clear 
+design and good testing. Make it right; then make it fast, if necessa
+ry."
-- Me
[download]

Make that:

perldoc perl
perldoc perldoc
[download]

To be more consistent, and portable.

*shrug*

When I learned perl, perldoc didn't work on about half the systems I used it with. ( I don't remember why; lazy sysadmins, perhaps). The man pages always worked.

Hence, the suggestions, by force of habbit.
--
Ytrew

http://juerd.nl/site.plp/perladvice

• a command line program that would change "black" to "regular" if followed or preceded by "coffee"
• a program to check the state of the S&P500 and DJI

I am not suggesting any obfu, I think a few or more complete and reasonably clear programs could fit on a 12 ounce mug.

I also like some of the insider Perlism's proposed but I don't know what suits your audience.

Be well,
rir

What would you consider cool on a mug?

s:g/5/6/;

Update: For the Perl 6 newbies out there, that's the Perl 6 way of writing s/5/6/g; :)

Okay... this is offically my first feable attempt at obfu... I sure someone can make a far better obfu then this...

$a = ".";for ($i=0; $i<20;$i++){print "$a";
}print"\n|\t\t   |\n|use strict;\t    ......\n|\t\t   |\t  |\n|\t\t   
+|\t  |\n|\t\t   |\t  |\n";
print "|\t\t   |......\n|\t\t   |\t\n|\t\t   |\t\n|\t\t   |\t\n";for (
+$i=0; $i<20;$i++) {
print "$a";
}
[download]

#!/usr/bin/perl -w
use strict;
[download]

Sounds like a great idea-and look forward to hearing what you decide upon.

Have you considered maybe a listing of (some, if not all of) the perl* docs that come in a standard distro (possibly with a brief description), so someone wondering where to look for something might be reminded which perldoc to look at? Just a thought.