comment on

Great thread hacker. The sentiment of what you're saying certainly rings true with this Perl journeyman. ++

I agree with what you're saying too l2kashe. However, I think the problem is more general than you suggest; perhaps a more holistic approach is needed for CPAN metadata?

I would like if the functionality of rt.cpan.org were more integrated in to the page for each distribution (or at least a link to the relevant rt.cpan.org page, so I don't have to dig it up), and to make it easier for people to post their sample code and other comments.

I note that there are a bunch of great ideas in schwern's CPANTS talk.

One just has to look at how the PHP online manual is done (look at the URL manual page as an example) to see another potential direction that this could be taken in.

In reply to Re: Re: Perl Monks += TMTOWTDI by DapperDan
in thread Perl Monks += TMTOWTDI by hacker

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Do you know where your variables are?
	PerlMonks