David Beaumont

It is technically possible, but it's generally not good for binaries which care about bytecode size, symbol counts, number of allocations during startup etc. Flogger's expected usage pattern (one logger...

Sadly not really. I'll update as soon as I have anything positive in this regard.

Wow, thanks for looking at this. Inside Google there's a quite sophisticated (but not error-prone) mechanism for doing migrations, and while the code itself is a bit hard to open-source,...

Just FYI, escaping in printf is done with '%', so: logger.atInfo().log("7. Single parameter, double-escaped anchor: %s \\%s", "abc"); Looks wrong to me, I think it should be: logger.atInfo().log("7. Single parameter,...

Ahh okay. It's just that as written: logger.atInfo().log("7. Single parameter, double-escaped anchor: %s \\%s", "abc"); would trigger a "too few parameters" error in our checks and the runtime code, since...

Thanks, I'll have a look. However I don't make any promises, especially since I think Flogger might need so refactoring (a big task) before it adheres to the rules about...

I'm afraid that Flogger does not accept external contributions without prior discussion of the changes being proposed. See the CONTRIBUTING.md file for more: > It's generally best to start by...

Thanks for noticing the date bug (this is a locale dependent bit of testing and should be changed to not rely on exact date formats).

Solving an "escaping" problem is not something you can do by changing the Flogger API. Flogger doesn't know or care where the logs go. The right place to care about...

Thanks. I will keep this around since I want to rethink allowing the MDC stuff anyway (I accept I was wrong to be not allowing existing Log4J users to continue...