[
https://issues.apache.org/jira/browse/LOG4PHP-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840707#action_12840707
]
Florian Platzer commented on LOG4PHP-98:
----------------------------------------
Of course you are right.
My keynote was to let the developers know that their great logging
configuration will not have an effect.
So I'm according to you, that inheriting is a nice way to do that. And at least
it should be possible to show this fail in the log-self debuglog
> Check for invalid names on getLogger call
> -----------------------------------------
>
> Key: LOG4PHP-98
> URL: https://issues.apache.org/jira/browse/LOG4PHP-98
> Project: Log4php
> Issue Type: Improvement
> Components: Code
> Reporter: Florian Platzer
> Priority: Trivial
>
> When calling the Logger::getLogger function a name-check would be helpful.
> So, if someone defines the logger "L1" and calls $_logger =
> Logger::getLogger('L2'); an exception could be thrown
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
