line |
stmt |
bran |
cond |
sub |
pod |
time |
code |
1
|
|
|
|
|
|
|
package Acme::this; |
2
|
|
|
|
|
|
|
$Acme::this::VERSION = '0.02'; |
3
|
1
|
|
|
1
|
|
1827
|
use strict; |
|
1
|
|
|
|
|
2
|
|
|
1
|
|
|
|
|
22
|
|
4
|
1
|
|
|
1
|
|
5
|
use warnings; |
|
1
|
|
|
|
|
1
|
|
|
1
|
|
|
|
|
63
|
|
5
|
|
|
|
|
|
|
|
6
|
|
|
|
|
|
|
sub import { |
7
|
1
|
|
|
1
|
|
55
|
print <
|
8
|
|
|
|
|
|
|
The Zen of Perl, by bellaire |
9
|
|
|
|
|
|
|
|
10
|
|
|
|
|
|
|
Beauty is subjective. |
11
|
|
|
|
|
|
|
Explicit is recommended, but not required. |
12
|
|
|
|
|
|
|
Simple is good, but complex can be good too. |
13
|
|
|
|
|
|
|
And although complicated is bad, |
14
|
|
|
|
|
|
|
Verbose and complicated is worse. |
15
|
|
|
|
|
|
|
Brief is better than long-winded. |
16
|
|
|
|
|
|
|
But readability counts. |
17
|
|
|
|
|
|
|
So use whitespace to enhance readability. |
18
|
|
|
|
|
|
|
Not because you're required to. |
19
|
|
|
|
|
|
|
Practicality always beats purity. |
20
|
|
|
|
|
|
|
In the face of ambiguity, do what I mean. |
21
|
|
|
|
|
|
|
There's more than one way to do it. |
22
|
|
|
|
|
|
|
Although that might not be obvious unless you're a Monk. |
23
|
|
|
|
|
|
|
At your discretion is better than not at all. |
24
|
|
|
|
|
|
|
Although your discretion should be used judiciously. |
25
|
|
|
|
|
|
|
Just because the code looks clean doesn't mean it is good. |
26
|
|
|
|
|
|
|
Just because the code looks messy doesn't mean it is bad. |
27
|
|
|
|
|
|
|
Reuse via CPAN is one honking great idea -- let's do more of that! |
28
|
|
|
|
|
|
|
EOF |
29
|
|
|
|
|
|
|
} |
30
|
|
|
|
|
|
|
|
31
|
|
|
|
|
|
|
1; |
32
|
|
|
|
|
|
|
|
33
|
|
|
|
|
|
|
__END__ |