[
https://issues.apache.org/jira/browse/LOG4PHP-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840709#action_12840709
]
Christian Hammers commented on LOG4PHP-98:
------------------------------------------
In my opinion the most important thing is that the user gets notified that he
misconfigured log4php or has a typo in his application because whatever we do,
it will not behave like he intended. As we cannot use the logger to report a
broken logging config, it should at least write the message
to stderr additionally. Apart from that I have no preference to one of the
proposals, just please don't silently ignore config errors.
> 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.
