I always copy one of the "most appropriate" other modules file structures of CPAN modules that I have and start making changes to that. At least that way it has all of the specifics that I need in my modules (e.g. copyright notice).

I think it is all about discipline, whether you use h2xs or your own solution.

One tip I've picked up from an article Johan Vromans wrote long ago: I have a "src" directory that contains all the sources of all modules that I work on. For each CPAN uploadable distribution I have a seperate directory structure. The .pm files in there are actually symlinks to the appropriate files in the "src" directory. This allows you to work from the distribution or from your "src" directory, whichever is more convenient to you at the time.

Liz

---

---

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.