"...every line is wrong..."

A programmer's fate.

This is the way i do it to avoid unnecessary trouble:

#!/usr/bin/env perl

use strict;
use warnings;

...;

__END__
[download]

Years ago i did it like this because i thought that it is more "readable":

#!/usr/bin/env perl

use strict;
use warnings;

MAIN: {

    ...;

}

sub foo { ...; }

sub bar { ...; }


__END__
[download]

It is not a bad idea to add a POD section after the __END__ token. See How can i debug compound map/grep statements just using print? for an example.

Please see also my, our, local, strict, warnings (already mentioned by others), diagnostics and perlpod.

And for a more detailed look "under the hood" see B::Deparse, B::Terse, B::Concise and Devel::NYTProf. choroba recently had a nice thread where you can see the B::* stuff at work: Using constants as hash keys.

Best regards, Karl