|Think about Loose Coupling|
Module Namespace, CPAN, and Linguisticsby Polyglot (Pilgrim)
|on May 19, 2009 at 04:36 UTC||Need Help??|
I'm putting together some routines for identifying characteristics of the Thai alphabet, making useful character classes, and may include some other nice features such as word splitting and/or sorting. I hope to package a module for CPAN from these, for the benefit of the Thai community.
CPAN recommends discussion regarding the NAMESPACE for each module, and I thought some of the monks here might have wisdom in this area.
If you see a module for a language, for example if a module were called "Swahili," what would you expect it to contain? For a rare language, will such a broad and generic name become "namespace pollution" later on? What about "Thai" vs "Thai::CharClass" etc.?
Perhaps many languages do not have modules named after them. Should I be looking instead at something like "Lingua::Thai::CharClass"? or does this seem like it gets too unwieldy?
Last but not least, if a previously created module (such as Lingua) becomes the base of the new namespace/module, does this mean that the developers would need to work together to accommodate the name? Since I have never created a module before, this is unclear to me...would I send the module to the authors of Lingua, for example, to be included in their package?
Thank you for your patience with this neophyte.