>>>>> "Knut" == Knut Urdalen <[EMAIL PROTECTED]> writes:
Knut> This topic has been discussed before [1]. But I want to
Knut> highlight it again since I'm working with the initial
Knut> functional version of the PHP 5 port and IF we should do any
Knut> changes to how log4php classes are named, this is the time
Knut> to do it. As I see it we have two reasonable options here:
Knut> 1) Keep the Logger* prefix as today. I haven't heard about
Knut> any conflicts with existing libraries.
Knut> Example: LoggerManager, LoggerAppenderFile,
Knut> LoggerPropertyConfigurator
Knut> 2) Rename all classes to use the PEAR naming convention [2].
Knut> Example: Log4PHP_Manager, Log4PHP_Appender_File,
Knut> Log4PHP_Configurator_Property
Knut> If we compare these alternatives to other libraries I see
Knut> that eZ components [3] use the first approach, while Zend
Knut> Framework [4] use the second approach. So the industry has
Knut> no concrete solution other than "prefix your classes".
Knut> I only found one documented advantage [5] of using the PEAR
Knut> naming convention over the current one.
Knut> What do you think? Which option would you like? Please cast
Knut> some votes with reasons so I know what you think.
If only there were namespaces...
Ok, although I hate names like Log4PHP_Configurator_Property, using
the PEAR convention helps avoiding conflicts. Apart from this
argument, it will be simple, fast and riskless to switch to namespaces
as soon as PHP includes this feature. Therefore I'd prefer the
second choice.
