You are viewing a plain text version of this content. The canonical link for it is here.

Posted to log4php-dev@logging.apache.org by "Joel Barnard (JIRA)" <ji...@apache.org> on 2012/10/13 22:30:03 UTC

[jira] [Commented] (LOG4PHP-121) Log4PHP classes should have namespace/package prefix

    [ https://issues.apache.org/jira/browse/LOG4PHP-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475708#comment-13475708 ] 

Joel Barnard commented on LOG4PHP-121:
--------------------------------------

Now that 2.3 has been released, has work begun on 3.0? 
I would be willing to do the refactoring to PHP namespaces, and PSR-2 if that has been decided.
                
> Log4PHP classes should have namespace/package prefix
> ----------------------------------------------------
>
>                 Key: LOG4PHP-121
>                 URL: https://issues.apache.org/jira/browse/LOG4PHP-121
>             Project: Log4php
>          Issue Type: Improvement
>          Components: Code
>         Environment: All
>            Reporter: Sean W. Quinn
>
> Looking through the Log4PHP classes it is quickly apparent that there is no prefix to the class names. The Log4PHP library should make use of PEAR style namespacing prefix (e.g. Apache_Log4PHP_) or, less likely PHP's added support for native namespaces (e.g. Apache\Log4PHP). Obviously the PEAR style namespace prefixing is more desirable as it does not restrict usage of Log4PHP to systems running PHP 5.3+.
> This would be an immense improvement, allowing already established code bases to tie Log4PHP into their own auto-loading framework and avoid potential class name conflicts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira