[Melbourne-pm] Namespace Guidelines?

[Kat Grant]

Hey Alfie,
Yep, definitely the first step is to move them into organisational  
namespace, but I'm looking for something that goes at bit further in  
good module naming practices.
I'm pretty sure I read something quite good years ago, but haven't  
been able to find it :(

K

On 29/12/2007, at 8:40 PM, Alfie John wrote:

> Hey Kat,
>
> Don't know of any guidelines off the top of my head that I could point
> you to, but why not start local packages with your own organisation
> name? That way, you're guaranteeing you won't be clashing with
> anything on CPAN.
>
> If that's too broad, you could do:
>
>   Org::Division::Branch::Package
>   Org::App::Object
>   Org::Division::App::Object
>
> Alfie
>
> On Dec 28, 2007 9:51 AM, Kat Grant <crashkat at gmail.com> wrote:
>> Hey All,
>> Hope everyone had a happy festive day :)
>>
>> Does anyone know of any nice articles outlining guidelines for OO
>> perl namespaces?
>>
>> At the moment, we have heaps of old code which is sitting in the top
>> level namespace and potentially clashing with cpan stuff, and also we
>> don't have things in any kind of namespace hierarchy - everything is
>> just in /lib. We want to clean this up and  I'm looking for something
>> I can refer to in our dev guidelines.
>>
>> Any help?
>>
>> Cheers
>> Kat
>> _______________________________________________
>> Melbourne-pm mailing list
>> Melbourne-pm at pm.org
>> http://mail.pm.org/mailman/listinfo/melbourne-pm
>>