logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Tuft Muller" <...@online.no>
Subject RE: Log4J encapsulation is poor
Date Thu, 03 Jan 2002 22:35:00 GMT
My guess is performance.

--

Thomas


| -----Original Message-----
| From: Christopher Randall [mailto:crandall@tivre.com]
| Sent: 03 January 2002 20:20
| To: Log4j-User (E-mail)
| Subject: Log4J encapsulation is poor
| 
| 
| I just have a question/comment about the Log4J code. It seems like there
| is a vast amount of exposure to instance variables in the code that I
| don't quite understand. I see a lot of public, package-access, and
| protected instance variables. Why does Log4J expose these data members?
| 
| Was this done for a specific purpose, or were the original authors just
| lazy coders? If there is a purpose, can someone please explain it to me?
| 
| Thanks,
| Chris
| 
| --
| To unsubscribe, e-mail:   
| <mailto:log4j-user-unsubscribe@jakarta.apache.org>
| For additional commands, e-mail: 
| <mailto:log4j-user-help@jakarta.apache.org>
| 
| 

--
To unsubscribe, e-mail:   <mailto:log4j-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:log4j-user-help@jakarta.apache.org>


Mime
View raw message