I can see strong arguments for making C6PAN a database for the reasons you give.

/perl/lib on the other hand - please no! Reasons:

• At the moment, if an error occurs in a module as a result of me passing a duff parameter, making a mistake in syntax etc, I type  vi, cut and paste the filename from the error message, and see the code straight away. Putting it into a database would significantly increase the overhead of that (start database client, spool to file, query, exit, read file....)
• Having some sort of database dependency (apart from potential cross platform problems) would potentially increase the footprint of a perl installation - which would present yet another obstacle to perl on small devices like PDAs.

---

---

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.