Re^2: Naming of modules that are mean to be inherited only?

Could I have an example name? If the main module is PDF::Puppy, and part of the code is in PDF::Puppy::Database, are you suggesting it could be named PDF::Puppy::DatabaseAbstract, or PDF::Puppy::Database::Abstract ?

Comment on Re^2: Naming of modules that are mean to be inherited only?

Replies are listed 'Best First'.
Re^3: Naming of modules that are mean to be inherited only? by Mutant (Priest) on Aug 14, 2007 at 12:30 UTC
I would prefer "PDF::Puppy::Database::Abstract". But as valdez mentioned, another option is to prefix 'Base', e.g. Base::PDF::Puppy::Database. In hindsight, I'd probably prefer that (or even prefixed Abstract::). However, there's no real convention here. The important thing is that it makes sense to you, it's fairly clear to anyone who might be maintaining your code in the future, and that you're consistent throughout your codebase.	[reply]

Replies are listed 'Best First'.

Re^3: Naming of modules that are mean to be inherited only?
by Mutant (Priest) on Aug 14, 2007 at 12:30 UTC

I would prefer "PDF::Puppy::Database::Abstract". But as valdez mentioned, another option is to prefix 'Base', e.g. Base::PDF::Puppy::Database. In hindsight, I'd probably prefer that (or even prefixed Abstract::).

However, there's no real convention here. The important thing is that it makes sense to you, it's fairly clear to anyone who might be maintaining your code in the future, and that you're consistent throughout your codebase.

[reply]