My style is easier seen than described, but I'd say my general rules are as follows.

• reads like natural language where appropriate: few abbreviations or multiple-crammed-words for names, postfix if when it reads better, method before Class when it reads better,
• interleave pod: name, synopsis, optional abstract, {globals}, {helpers}, methods/functions {pod, code, ...}, description, see also, license/author,
• help the smart editor within reason: curlies aligned vertically, not afraid to use vertical space, escape properly for weaker color-coders,
• hash+dash*76 visual cut-here lines to delineate logical sections,
• standard #TODO: #REVIEW: #HACK, #BUG: comment keywords for future planning and scanning,

My perltidy does the token-level style: http://www.halley.cc/ed/linux/configs/

See a reasonable example of my style on CPAN in Data::Binder or Data::Favorites.

e d @ h a l l e y . c c

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.