You are viewing a plain text version of this content. The canonical link for it is here.

Posted to log4php-dev@logging.apache.org by "Sven Rautenberg (JIRA)" <ji...@apache.org> on 2012/06/23 11:13:42 UTC

[jira] [Commented] (LOG4PHP-98) Check for invalid names on getLogger call

    [ https://issues.apache.org/jira/browse/LOG4PHP-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399892#comment-13399892 ] 

Sven Rautenberg commented on LOG4PHP-98:
----------------------------------------

I second the argument against a warning, because using a logger does not mean it has been intentionally configured. -> wontfix
                
> 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
>    Affects Versions: 2.0.0
>            Reporter: Florian Platzer
>            Priority: Trivial
>              Labels: call, check, fail, function, getlogger, initiate, instance, name
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira