Mark Womack wrote:
> > I have wondered about this as well for other cases. It would be useful to > have some code that searches the classpath for classes that implement a > given interface/class. But I think that this code would be very time > consuming, searching the entire classpath, inspecting all the classes. If > you think of a good way, I think we would all like to hear about it. Yes, searching the classpath would be time consuming. Fortunately, it would happen only during PatterLayout setup. Unfortunately, that setup can occur at any time. If I come up with a good solution, this dev list will be one of the first places I go to tell about it. > > >>>But frankly, I think that doing this is not required to >> >>accept Mike's first >> >>>round of changes he has submitted. >> >>This would be nice. I've imported the current 1.3 code to my >>machine, >>and I have looked at how some of the proposed changes might >>affect other >>classes. For example, I think that my ideas would require changes to >>o.a.l.helpers.FormattingInfo. Since this class is only usable within >>its package (even though the class itself is public) I don't expect >>changes to it to break other code. However, I don't know if >>there are >>any implementations of Log4J with new classes added to the the Log4J >>packages. I don't think I've seen anything in the documentation >>discouraging creating classes in packages already found in the Log4J >>distribution. >> >>Is this a situation about which I should be concerned? > > > Do you think your first round of changes will affect the > o.a.l.helpers.FormattingInfo? Can you elaborate? No, the changes I am contemplating for Conversion Words will probably require changes to FormattingInfo. > > And I don't know what the policy is on this. Anyone can write classes that > end up in the same package, and thus have access to package level > classes/members. Ceki, are we trying to maintain api compatibility at that > level? > -- Cheers, Mike McAngus [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
