Hi Will,
On Mon, 2007-07-30 at 13:57 -0500, Will Fitch wrote:
> Thanks, Marcus. I finally found this documentation on PECL by using Google
> site:pecl.php.net.
>
> I appreciate the insight.
it's also part of the PHP Source distribution and CVS:
http://cvs.php.net/viewvc.cgi/php-src/CODING_STAND
Thanks, Marcus. I finally found this documentation on PECL by using Google
site:pecl.php.net.
I appreciate the insight.
On 7/30/07, Marcus Boerger <[EMAIL PROTECTED]> wrote:
>
> Hello Will,
>
>
> our CODING_STANDARDS says: Classes should be given descriptive
> names...Each word should start
I agree on both the naming convention (log4j_*), as well as the standard
naming convention. There seems to be plenty of sources to suggest different
things, but no official declaration within PECL.
On 7/26/07, Richard Lynch <[EMAIL PROTECTED]> wrote:
>
> On Wed, July 25, 2007 6:20 pm, Will Fitch
On Wed, July 25, 2007 6:20 pm, Will Fitch wrote:
> And the list goes on. I have attached a text file with all 1.4
> specifications of log4j. I considered log4p_* as a prefix for all
> class
> names, but I am concerned for Java developers moving to PHP who are
> familiar
> with the standard alread
Hello All,
I am continuing my Log4J implementation for PHP. There are some naming
conventions which I am concerned will cause existing userspace class issues.
If you are familiar with Log4J, the following example class names won't be
new to you:
Agent
Logger
Appender
Constants
FileApp
