Hello again folks (if anyone read the last post - busy time of year),
I’ve completed some work on Log4r, and would like to share it soon with
the Ruby community, after I’ve done the rest. I don’t have access to
the Log4r code repository … any hints on getting in contact with
project owner(s) would be great.
Accomplished in initial round of Log4r refactoring:
- converting the tests over to Test::Unit
- changed all existing tests (except 1) so they are self-verifying and
can be run at any point as a complete test suite (previous tests had to
be verified visually)
- added new tests to the suite to help guide my refactoring, which
clarify the intent of the code
- various refactorings large and small
Remaining to do’s:
- continue refactoring
- reduce coupling/global state of program to simplify code, clarify
- introduce some Log4J-type behaviour which I miss (I know that Log4R
didn’t slavishly follow Log4J, but J does have some nice features)
I’m doing this for my own benefit and for my work, but would like to
share with the community. I believe that my work is useful – even if
only for me.
Warning: I think I might have to change the Logger.initialize() method,
which means that existing code that creates loggers like Logger.new(
‘a’, WARN, etc) would break … but code using XML or YAML
configuration would still work. If this is hugely problematic, I’d be
open to discussion.
Lastly, I still can’t get a hold of Leon T. … any ideas where he
can be reached?