Hello guys,
first of all, i think it's great that there are, after some months (or
years? ;)), be a bunch of guys, that will work again on this project.
I'm using log4php since year or so, fix some bugs from the latest
trunk and adding the one or other appender for some projects.
I ask marco last week, if there is a way where i can support this
project, and he linked me to this mailinglist.
So, to the threat-theme.
I'm for the first and classic choice. So, why did the newbie stand up
against the others? The short way:
1) i don't like PEAR. It is not verry clean and have a lack of
supporting itself in different versions. I don't liek pear! ;)
2) there are much more things to do than change a commonly, trough
years, used name-pattern
3) Namespaces are a important point, right. But since nobody knows if
there will be any support and how the support looks like in the future
php-versions, we don't really have to consider them
Greets,
Thomas Sittig
This topic has been discussed before [1]. But I want to highlight it
again since I'm working with the initial functional version of the PHP 5
port and IF we should do any changes to how log4php classes are named,
this is the time to do it. As I see it we have two reasonable options here:
1) Keep the Logger* prefix as today. I haven't heard about any conflicts
with existing libraries.
Example: LoggerManager, LoggerAppenderFile, LoggerPropertyConfigurator
2) Rename all classes to use the PEAR naming convention [2].
Example: Log4PHP_Manager, Log4PHP_Appender_File,
Log4PHP_Configurator_Property
If we compare these alternatives to other libraries I see that eZ
components [3] use the first approach, while Zend Framework [4] use the
second approach. So the industry has no concrete solution other than
"prefix your classes".
I only found one documented advantage [5] of using the PEAR naming
convention over the current one.
What do you think? Which option would you like? Please cast some votes
with reasons so I know what you think.
Regards,
Knut Urdalen
[1] http://marc.info/?l=log4php-dev&m=113707705331229&w=2
[2] http://pear.php.net/manual/en/standards.naming.php
[3] http://svn.ez.no/svn/ezcomponents/trunk/
[4] http://framework.zend.com/svn/framework/trunk/library/
[5]
http://www.phpkitchen.com/index.php?/archives/663-Advantages-of-using-the-PEAR-class-naming-convention.html
