note
rcaputo
<p>[BUU] writes:<blockquote><i>I will note in passing that there are lots of modules that have a proper name in the title, but mostly these are named after systems of some sort, most notably POE has it's own namespace.</i></blockquote></p>
<p>[cpan://POE] components tend to have "POE" in their names because they don't live separate lives from that framework. The implication is "You need POE to use this." In that vein, BUU::IRC implies that some BUU module is necessary to use it.</p>
<p>On the other hand, modules based on POE aren't required to be in POE's namespace. People just feel strongly enough about the association to insist on putting them there. So strongly in fact that the [cpan://POE::Component] namespace was set aside to let them without conflicting with the framework itself. From POE::Component's documentation:</p>
<blockquote>The POE::Component namespace was started as place for contributors to publish their POE-based modules without requiring coordination with the main POE distribution.</blockquote>
<p>[cpan://Term::Visual] is a notable exception. It provides a three- or four-section terminal interface (title line, scrolling terminal region, status bar, input line). To come full-circle, I think [japhy] has written an actual IRC client using it and [cpan://POE::Component::IRC].</p>
<p><tt>-- Rocco Caputo - [http://poe.perl.org/]</tt></p>
391394
391394