Re: Testing_Selenium and important naming conventions

Hi, Greg.

Testing_Selenium is the right name, please go ahead and rename.

I've just commited to CVS server the one which has Testing_ prefix. I already ran the tests, and it seems to fine. I think I can change anytime. But, I would like to know what to do with CVS repository, because it is not Testing_Selenium, but Selenium. If there is no problems, I would like to have Testing_Selenium repository. Can I make the Testing_Selenium repository and commit the source code there? Thanks, Shin

The coding standards for PHP Internals include explicit definition of names that will occur in all future PHP classes. Here is the relevant section: [7] Classes should be given descriptive names. Avoid using abbreviations where

    possible. Each word in the class name should start with a capital

letter,

    without underscore delimiters (CampelCaps starting with a capital

letter).

    The class name should be prefixed with the name of the 'parent set'

(e.g.

    the name of the extension).

    Good:
    'Curl'
    'FooBar'

    Bad:
    'foobar'
    'foo_bar'

Here is a link to the whole definition of coding standards: http://cvs.php.net/viewvc.cgi/php-src/CODING_STANDARDS?revision=1.32.4.3&view=markup As such, if we always put an underscore in our class names, it will be guaranteed not to conflict with the internals classes. By the way, all active PEAR developers should either skim php.internals at news.php.net, or subscribe to php-internals@lists.php.net, it is not good to be unaware of what is going on behind the scenes while developing packages to extend functionality of PHP itself! Greg -- PEAR Development Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php

-- Shin OHNO http://www.ganchiku.com/