On Sat, Aug 12, 2017 at 1:30 PM, Dominik Psenner <dpsen...@gmail.com> wrote:
> If it is a private class it might not be sensible to have that class name > in the logfiles. If it is public the class could and should probably be > refactored. ;-) > > I'm only a little afraid of the dollar sign. It is often a bash variable > and thus bound to be typo prone when used for greps, configurations, .. > > Could a logger name attribute be an option? > What do you mean? Gary > > 2017-08-12 20:44 GMT+02:00 Gary Gregory <garydgreg...@gmail.com>: > > > Hi, > > > > Why does that matter? > > > > Gary > > > > On Aug 12, 2017 12:34, "Dominik Psenner" <dpsen...@gmail.com> wrote: > > > > > Are the nested classes private or public? > > > > > > 2017-08-12 20:29 GMT+02:00 Gary Gregory <garydgreg...@gmail.com>: > > > > > > > Hi All, > > > > > > > > I you use nested classes to build loggers, you end up with logger > names > > > > like A$N1, A$N2 and so on. > > > > > > > > If you then set a logger level in a config using "A", it does not > > affect > > > > A$N1 and A$N2 as you might expect, since "$" is not a ".". > > > > > > > > What about treating "$" like a "."? > > > > > > > > Thoughts? > > > > > > > > Gary > > > > > > > > > > > > > > > > -- > > > Dominik Psenner > > > > > > > > > -- > Dominik Psenner >
