Re: [Phpwebsite-developers] Class Naming

[Steven L. <st...@tu...>]

+1 from me :)

> Ok so we are using PHPWS_classname as the naming standard. However, I
> would like to note that while we may be using multiple classes to define
> our module, it is equally important to name the subclasses after the
> final class.
>
> For example, for the recoding of the FatCat module I have:
> PHPWS_Fatcat
>
> but it extends
> PHPWS_Category
> PHPWS_Elements
>
> Not good as someone else may try to use those names. So I changed it to:
> PHPWS_Fatcat_Category
> PHPWS_Fatcat_Elements
>
> It is a little more clunky but I believe it will save headaches in the
> long run.
>
> Please vote on the standard.
>
> Matthew McNaney
> Internet Systems Architect
> Electronic Student Services
> Email: ma...@tu...
> URL: http://phpwebsite.appstate.edu
> Phone: 828-262-6493
> ICQ: 141057403
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers


-- 
Steven Levin
Electronic Student Services
Appalachian State University
Phone: 828.262.2431
PhpWebsite Development Team
URL: http://phpwebsite.appstate.edu
Email: st...@NO...