[
https://issues.apache.org/jira/browse/LOG4PHP-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086853#comment-13086853
]
Ivan Habunek commented on LOG4PHP-121:
--------------------------------------
Well, log4php already uses a class prefix: "Logger". I know it's not ideal, but
this should eliminate a majority of potential naming conflicts.
Frankly, this change would require a lot of work, and it would also break
backward compatibility. This is the time which IMHO could better be spent
cleaning up our code base (which is still a bit of a mess), improving
performance and adding new features.
I would presonally like to start using php namespaces at some point in the
future, since it's a lot nicer than the pear naming convention. However, as you
said, that cannot be done until most people switch to PHP 5.3+.
<self-promotion>
BTW, did you know you can now get log4php from our pear repository?
http://pear.apache.org/log4php/index.html
</self-promotion>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
