Skip Menu |

This queue is for tickets about the Log-Log4perl CPAN distribution.

Report information
The Basics
Id: 45604
Status: resolved
Priority: 0/
Queue: Log-Log4perl

People
Owner: Nobody in particular
Requestors: TIMB [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: (no value)
Fixed in: (no value)



Subject: Most uses of "inheritance" in the docs really mean "namespace hierarchy"
For example: "Log::Log4perl works with inheritance: The config file above didn't specify anything about My::MegaPackage. And yet, we've defined a logger of the category My::MegaPackage. In this case, Log::Log4perl will walk up the class hierarchy (My and then we're at the root)" This is confusing. The fact that A::B::C falls back to A::B and then A has nothing to do with inheritance or "class hierarchy" of those modules. s/inheritance/the namespace hierarchy of your packages/ s/walk up the class hierarchy/walk up the package namespace hierarchy/ Similar phases crop up elsewhere in the docs.
You're right, it's confusing. The term is borrowed from log4j and not to be confused with Perl's class hierarchy: http://logging.apache.org/log4j/1.2/manual.html "The inherited level for a given logger C, is equal to the first non-null level in the logger hierarchy, starting at C and proceeding upwards in the hierarchy towards the root logger." I've added a bit of clarification to the docs: http://github.com/mschilli/log4perl/commit/4cb91d260f5b18796593d45485b2f182681b1977