You always read the source before you install.. ?

Admit it, that's an exageration.
You did not read the source of the modules you have installed.

Nobody here has 'always read the source' before they install. You read the docs, you get suggestions from peers on what to use.. You have feel for it.. etc. You can tell when a distro has been cared for, and when it has been thrown up on cpan.

Every now and then I'll see something on cpan that's obviously been built by someone way cool who knows way more than I do about xyz, but the lack of doc turns me off. The lack of proper distro(ing(?)).

When I come across a module that's built by someone who doesn't have much out there- if the thing is well documented and the distro has been cared for, I have absolutely no qualm about installing it and trying it out.

Now, that's me. That was an example of how someone goes about installing stuff.

Sometimes I snoop at the code, sure. Sometimes because it's someone with class and I admire how they do xyz, or maybe I want to know about the magic of what's going on.

But for pete's sake- What you're alluding to is actually reading and I assume understanding, code for stuff like DBI, Storable (I think that must have some creepy XS in it, no?)- Smart::Comments, and gosh knows what else. Unless of course you haven't installed DBI, CGI, and HTML::Template because you haven't had the time to read the source yet.

I take issue with your statement. Because a lot of the people we have here are starting out or maybe never had peers to make suggestions and point out methods of learning and growth- and your suggestion that;

• a) to see the source with syntax highlighting, you should use this javascript plugin = is merely an option, and in my view for one- a retarded one (and misleading) when you have the tools you need much more readily and reliably available
• b) you read the source before you install- is ridiculous- unless you are documenting cpan itself and you have a team of monkeys backing you up.

Now, maybe I am misunderstanding your statements. If so, please excuse me and do clarify.

---

---

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.