Robert Hicks wrote:
> Do you tend to make your module names generic like "Site" or "Webapp"? I
> am doing a couple small sites and I am creating secondary modules to
> hold things.
>
> I have something like:
>
> Site.pm
> Site::Actions.pm
> Site::Validators.pm
> Site::SQL.pm
>
> Is that good? Or would you replace "Site" with something?
I tend to use this now for small projects
Client::sub_project::Public.pm
Client::sub_project::Admin.pm
There's also:
cgi-bin/sub_project/index.cgi
Templates/sub_project/foo.tmpl
This violates the rule of thumb of using all-lower module names, but it
makes it very clear how different parts of a larger project relate.
I would even us this design even if there was one "sub project", because
it's easy enough to do, and I never no when the second project will appear.
Mark
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/suppressed/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.