Re: trigger errors

2011-11-13 Thread Florian Semm
Am 13.11.2011 10:54, schrieb Ivan Habunek: On 13 November 2011 09:25, Florian Semm wrote: if we expect in a configuration an attribute like "name" or "class" and we got nothing, we should call this trigger_error() function. i haven't seen that the LoggerConfigurator class validate the configur

Re: trigger errors

2011-11-13 Thread Ivan Habunek
On 13 November 2011 09:25, Florian Semm wrote: > if we expect in a configuration an attribute like "name" or "class" and we > got nothing, we should call this trigger_error() function. > > i haven't seen that the LoggerConfigurator class validate the configuration. > The configurator still trigger

[jira] [Commented] (LOG4PHP-152) A rewrite of the configurator

2011-11-13 Thread Ivan Habunek (Commented) (JIRA)
[ https://issues.apache.org/jira/browse/LOG4PHP-152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13149268#comment-13149268 ] Ivan Habunek commented on LOG4PHP-152: -- The new code has been merged with trunk. It

Re: trigger errors

2011-11-13 Thread Florian Semm
Am 12.11.2011 20:40, schrieb Christian Grobmeier: On Sat, Nov 12, 2011 at 8:36 PM, Ivan Habunek wrote: On 12 November 2011 20:31, Christian Grobmeier wrote: Good question. In my world logging framework should never break an application. So... what exactly is an error? A console output? stand