[prev in list] [next in list] [prev in thread] [next in thread] 

List:       log4php-dev
Subject:    [jira] [Commented] (LOG4PHP-121) Log4PHP classes should have namespace/package prefix
From:       "Ivan Habunek (JIRA)" <jira () apache ! org>
Date:       2012-10-20 9:48:14
Message-ID: 1372525102.5053.1350726494096.JavaMail.jiratomcat () arcas
[Download RAW message or body]


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

Ivan Habunek commented on LOG4PHP-121:
--------------------------------------

I'm planning on making the initial push next month, after ApacheCon (anybody \
coming?).

Sven, codesniffer already has built-in PSR standards (added a little while back), so \
no need for external projects: \
https://github.com/squizlabs/PHP_CodeSniffer/tree/master/CodeSniffer/Standards

Also, there is a coding standard fixer project which can apply mandatory PSR-2 \
formatting automatically: http://cs.sensiolabs.org/

I already started a sandbox project to try out various technologies planned for 3.0. \
It's not in the official repo yet since I'm just trying things out. Have a look here: \
https://github.com/ihabunek/log4php3

Suggestions are welcome.
                
> 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


[prev in list] [next in list] [prev in thread] [next in thread]