>>>>> On Tue, 30 May 2000 17:06:58 -0400, Robert Kiesling <[EMAIL PROTECTED]>
>said:
> I have two module projects in the works: one to implement an
> text editing workspace, and another to create a Browser for
> the Perl class library. I would like to call them Workspace.pm
> and Browser.pm, but would like any feedback that you would
> care to offfer.
I think, writing something for many or even all browsers, justifies
the namespace Browser, writing something for many or even all
workspaces, justifies the namespace Workspace, but writing a browser
or a workspace never justifies the namespaces Browser and Workspace
respectively. Just like a car is usually branded with a name, browsers
and workspaces should be branded too.
Let me illustrate how I personally deal with namespaces. When I'm
writing something bigger, I usually proceed by starting with a private
namespace, i.e. anything containing an underscore, e.g. the company
name that pays for the work and the codename. So I get names like
woolworth_billing, phillips_catalog or anderson_statistics
(disclaimer: names changed to protect the innocent:-). If such a
project gets shape and it makes sense to publish it, it is extremely
easy to rename the whole thing in one go with simple search and
replace.
Hope that helps,
--
andreas
