Now I understand what you mean :) I think, however, that such parser should also handle variable substitution, forcing me to reinvent a wheel, right? So I think that it is better to stick with Log4perl internal classes (those classes should be "future-proof"), hence the solution above.
|Replies are listed 'Best First'.|
Re^5: Accessing Log::Log4perl Configuration Values
by andyford (Curate) on Mar 19, 2007 at 15:14 UTC