comment on

You’re replying to a 10 year-old node from a monk who has been absent for 6 years.

I'm just jumping on the bandwagon after some other anon resurrected the node. As for the whereabouts of OP, who really knows? I've had accounts on this site that make it look like I've been absent for well over a decade. But the OP is irrelevant now that LanX has been inspired to consult an ontology expert on the feasability of fixing CPAN. I know it's feasable because I've implemented an automated ontology to browse thousands of installed modules, which I use daily, and would feel somewhat lost without.

Module curation does sound like a really good idea.

That's what I wanted to hear! Thank you for listening.

In reply to Re^3: Top Level Module Namespace Table by Anonymous Monk
in thread Top Level Module Namespace Table by Xiong

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.


Your skill will accomplish what the force of many cannot
	PerlMonks