Arthur T. Murray wrote: > http://mind.sourceforge.net/mindloop.html is an AI Mind flowchart > that suggests the following namespaces for main modules of an AI:
With all due respect, any such modules should not go under AI, they should go in a dedicated top-level space, e.g. Mindloop::. Unless they're usable outside the Mindloop framework, that is. > ... > AI::MOTORIUM Not familiar with Perl module naming conventions, eh? Pay attention to case. "...::Motorium" would be much preferred. > Could somebody please explain for me and others what is the system > of pre-existing AI namespaces in Perl? For AI in particular, next to none. For general guidelines on module naming in Perl, please read the doc for the Perl Authors Upload Server: http://www.cpan.org/modules/04pause.html especially sections 5, 6 and 7. And also, read The Perl Module List: http://www.cpan.org/modules/00modlist.long.html especially Part 1. > ...it intrigues me to discover here the > possibility that module names may already be "firming up" in Perl. Not really. Not like Sun controls Java namespaces. Basically, if no one has taken it yet, it's up for grabs; but within the rules defined in the above documents. If you're serious about making these things available via CPAN, and you want to play nice, it's critical to discuss your module naming with the guys on [EMAIL PROTECTED] (but read the above docs first). If you *don't* want to play nice, well, no one can stop you from naming your modules however you want. (I don't know if Sourceforge has perl module naming policies.) One thing about it that may be somewhat comforting: If you have a standalone framework (such as this Mindloop thing might be), you can safely assume that a sufficiently unique top-level name (e.g. "Mindloop") can be yours for the taking, and then you can shove all the related modules under it. (But you *still* should discuss it on [EMAIL PROTECTED] first.) hth, John Douglas Porter
