So you propose an inversion here? Won't that break as many modules making the (currently) correct assumptions, w.r.t. config data?
Logs are created *from* values in the configuration, ergo they should go away *before* the values that created them are also destroyed.
E.g., if my module creates a log file, and points at the name of that log, then the name of that log cannot become invalid before that log file is destroyed and cleared.
Bill
Yea, I woke up this morning thinking about this. This patch stands to break more than it fixes and it certainly breaks precedence. I suspected as much which is why I posted the patch. Thanks for the comments.
-1
Bill
